paperclipai/paperclip / .agents/skills/check-pr
check-pr
VerifiedCheck a GitHub, GitLab, or Perforce PR/MR/CL for review comments, failing checks, and PR-body gaps. Use when asked to inspect, fix, or prepare a change for submission.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 14.3 KB |
| references/gitlab-api.md | markdown | 2.5 KB |
| references/graphql-queries.md | markdown | 2.0 KB |
references/gitlab-api.md
View on GitHub# GitLab API Reference
Useful GitLab REST API calls for working with merge request discussions, using `glab api`.
`glab api` automatically resolves `:fullpath` to the URL-encoded project path from the local git remote.
## Fetch MR details
```bash
glab mr view <MR_IID> --output json
```
Key fields (compared to GitHub equivalents):
- `iid` - internal MR number (use this, not `id`)
- `source_branch` - equivalent to GitHub's `headRefName`
- `sha` - HEAD commit SHA, equivalent to GitHub's `headRefOid`
- `description` - equivalent to GitHub's `body`
## Fetch all discussions (inline + general comments)
```bash
glab api "projects/:fullpath/merge_requests/<MR_IID>/discussions?per_page=100"
```
Paginate with `&page=2`, `&page=3`, etc. until the response array length is less than `per_page`.
Each discussion object:
- `id` - discussion ID (used for resolution)
- `resolved` - `true` or `false`
- `notes` - array of note objects
Each note object:
- `type` - `"DiffNote"` for inline diff comments, `null` for general comments
- `author.username` - author's username
- `body` - comment text
- `position.new_path` - file path (for `DiffNote` type)
## Filter for unresolved inline diff comments
```bash
glab api "projects/:fullpath/merge_requests/<MR_IID>/discussions?per_page=100" | \
jq '[.[] | select(.resolved == false and (.notes[0].type == "DiffNote"))]'
```
## Resolve a single discussion
```bash
glab api --method PUT \
"projects/:fullpath/merge_requests/<MR_IID>/discussions/<DISCUSSION_ID>" \
--field resolved=true
```
There is no batch resolution in GitLab - issue one PUT per discussion.
## Fetch pipeline status for an MR
```bash
glab api "projects/:fullpath/merge_requests/<MR_IID>/pipelines"
```
Pipeline statuses: `running`, `pending`, `success`, `failed`, `canceled`, `skipped`.
## Fetch jobs for a specific pipeline
```bash
glab api "projects/:fullpath/pipelines/<PIPELINE_ID>/jobs"
```
Each job has `name`, `status`, `stage`, and `web_url`.
## Fetch MR notes (general comments and bot reviews)
```bash
glab api "projects/:fullpath/merge_requests/<MR_IID>/notes?per_page=100"
```
Filter by `author.username` to find Greptile bot comments. The exact bot username depends on the Greptile installation - check the first Greptile comment to identify it.
## Post a comment on an MR
```bash
glab mr note <MR_IID> --message "your message here"
```
Or via API:
```bash
glab api --method POST \
"projects/:fullpath/merge_requests/<MR_IID>/notes" \
--field body="your message here"
```
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |