Agent skill

Check PR

by onyx-dot-app in onyx-dot-app/onyx

Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.

MITAuto-check passedDevelopment

Install Check PR

skills CLI
$ npx skills add onyx-dot-app/onyx --skill check-pr -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install onyx-dot-app/onyx check-pr --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/onyx-dot-app/onyx.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/greptile/check-pr .claude/skills/check-pr && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
check-pr
GitHub stars
32k
Used in
2 other repos
Token cost
~2.3k tokens
SKILL.md length
833 words
Files
3 (incl. references)
Skills in repo
9
Repo updated
First seen
Licence
MIT

At a glance

Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.

  • Works in 10 steps: Detect platform → Identify the PR/MR/CL → Fetch PR/MR/CL details → …
  • The user wants to check a PR/MR/CL
  • SKILL.md covers Inputs, Instructions and Output format
  • Calls gh, glab and git

What it does

Check PR is an agent skill from onyx-dot-app/onyx. Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions. Waits for pending checks to complete, categorizes issues as actionable or informational, and optionally fixes and resolves them. Use when the user wants to check a PR/MR/CL, address review feedback, or prepare a change for submission.

Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/gitlab-api.md` and `references/graphql-queries.md`). Compatibility notes: Requires git and gh (GitHub CLI), glab (GitLab CLI), or p4 (Perforce CLI) installed and authenticated.

It sits in Development, covering Pull requests. It works with GitLab and GitHub. The repository describes itself as: Open Source AI Platform - AI Chat with advanced features that works with every LLM. The licence is MIT.

When your agent uses it

  • The user wants to check a PR/MR/CL
  • Address review feedback
  • Prepare a change for submission

Example prompts

  • “Use the check-pr skill to check a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review…”
  • “/check-pr”

Requirements

  • Compatibility (from SKILL.md): Requires git and gh (GitHub CLI), glab (GitLab CLI), or p4 (Perforce CLI) installed and authenticated.
  • Pre-approved tools (allowed-tools): Bash(gh:*), Bash(glab:*), Bash(git:*), Bash(p4:*)

Workflow steps

10 steps, taken from the step headings in SKILL.md.

  1. Detect platform
  2. Identify the PR/MR/CL
  3. Fetch PR/MR/CL details
  4. Wait for pending checks
  5. Analyze the PR/MR
  6. Categorize issues
  7. Report findings
  8. Fix issues (if requested)
  9. Resolve review threads
  10. Multiple PRs/MRs/CLs

What it can do on your machine

Read from SKILL.md and the folder at commit d83b611. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash(gh:*)
    • Bash(glab:*)
    • Bash(git:*)
    • Bash(p4:*)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • gh
    • glab
    • git
    • jq

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use gh, glab and git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Requires git and gh (GitHub CLI), glab (GitLab CLI), or p4 (Perforce CLI) installed and authenticated.

    From compatibility in the SKILL.md frontmatter.

Context cost

Check PR loads about 2.3k tokens when it runs, and up to ~3.5k if it reads all its reference files. Until then it costs about 107 tokens; SKILL.md has 833 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~107
When it runs · the whole SKILL.md, loaded when a task matches
~2.3k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from onyx-dot-app/onyx at commit d83b611, republished under its MIT licence (© onyx-dot-app). 833 words, ~2,321 tokens.

Download SKILL.mdSave it as .claude/skills/check-pr/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
check-pr
description
Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions. Waits for pending checks to complete, categorizes issues as actionable or informational, and optionally fixes and resolves them. Use when the user wants to check a PR/MR/CL, address review feedback, or prepare a change for submission.
allowed-tools
Bash(gh:*), Bash(glab:*), Bash(git:*), Bash(p4:*)
compatibility
Requires git and gh (GitHub CLI), glab (GitLab CLI), or p4 (Perforce CLI) installed and authenticated.
license
MIT
metadata.author
greptileai
metadata.version
1.3

Check PR

Analyze a pull request (GitHub), merge request (GitLab), or shelved changelist (Perforce) for review comments, status checks, and description completeness, then help address any issues found.

Inputs

  • PR/MR/CL number (optional): If not provided, detect the PR/MR for the current branch, or the default pending changelist for p4.

Instructions

0. Detect platform

First check if the user is working in a Perforce depot by looking for a .p4config file or P4CLIENT/P4PORT environment variables:

bash
# Check for Perforce environment
if p4 info >/dev/null 2>&1; then
  VCS="perforce"
else
  # Fall back to git remote detection
  REMOTE_URL=$(git remote get-url origin)
  if echo "$REMOTE_URL" | grep -qi "gitlab"; then
    VCS="gitlab"
  else
    VCS="github"
  fi
fi

For self-hosted GitLab instances whose hostname doesn't contain "gitlab", the user can override by passing --vcs gitlab as an input. For Perforce, the user can override by passing --vcs perforce.

1. Identify the PR/MR/CL

If a number was provided, use it. Otherwise, detect it:

GitHub:

bash
gh pr view --json number -q .number

GitLab:

bash
glab mr view --output json | jq '.iid'

Perforce:

bash
# List pending changelists for the current user/client
p4 changes -s pending -u $P4USER -c $P4CLIENT

Key field differences between platforms:

  • GitHub: number, headRefName, headRefOid
  • GitLab: iid, source_branch, sha
  • Perforce: changelist number (CL), shelved files for in-review CLs
2. Fetch PR/MR/CL details

GitHub:

bash
gh pr view <PR_NUMBER> --json title,body,state,reviews,comments,headRefName,statusCheckRollup
gh api repos/{owner}/{repo}/pulls/<PR_NUMBER>/comments
gh api --paginate "repos/{owner}/{repo}/issues/<PR_NUMBER>/comments?per_page=100"

GitHub PRs are also issues, so general PR comments live on the issue comments endpoint. Greptile may edit a single general PR comment on each review cycle instead of creating a new review or comment. Always inspect the latest Greptile-authored general comment by updated_at, including any "Prompt to fix all with AI" section, before concluding that the PR is clear.

GitLab:

bash
glab mr view <MR_IID> --output json
# Fetch discussions (inline diff comments are type "DiffNote"; general comments have null type)
glab api "projects/:fullpath/merge_requests/<MR_IID>/discussions"

For GitLab, paginate discussions if needed (add ?per_page=100&page=N).

Perforce:

bash
# Get changelist description, files, and status
p4 describe -s <CL_NUMBER>

# Get shelved files (for in-review CLs)
p4 describe -S <CL_NUMBER>

# Get the diff of the shelved changelist
p4 diff2 //...@=<CL_NUMBER> //...@=<CL_NUMBER>

# List review comments (if using p4 review workflow)
p4 review -c <CL_NUMBER>

Key Perforce CL fields:

  • Change: changelist number
  • Status: pending, submitted, shelved
  • Description: the CL description / commit message
  • Files: list of files in the CL
3. Wait for pending checks

Before analyzing, ensure all status checks have completed. If any checks are PENDING or IN_PROGRESS (GitHub) / running or pending (GitLab), poll every 30 seconds until all checks reach a terminal state.

GitHub: poll statusCheckRollup from gh pr view.

GitLab:

bash
glab api "projects/:fullpath/merge_requests/<MR_IID>/pipelines"

Pipeline statuses: running, pending, success, failed, canceled, skipped. Poll until no pipeline has running or pending status.

Perforce: Perforce doesn't have built-in CI checks natively. If the team uses a review tool (Swarm, etc.) or an external CI triggered by shelve events, check the relevant system. Otherwise, proceed to analysis immediately.

4. Analyze the PR/MR

Once all checks are complete, evaluate these areas:

A. Status Checks
  • Are all CI checks passing?
  • If any are failing, identify which ones and the failure reason.
B. PR/MR Description
  • Is the description complete and follows team conventions?
  • Are all required sections filled in?
  • Are there TODOs or placeholders that need updating?
C. Review Comments
  • Inline code review comments that need addressing
  • Look for bot review comments (e.g. from greptile-apps[bot] on GitHub, or the Greptile bot user on GitLab, linters, etc.)
  • Human reviewer comments
  • Perforce: review comments from p4 review or external review tools
D. General Comments
  • Discussion comments on the PR/MR
  • For GitHub, check the issue comments endpoint and use updated_at to catch bot comments edited in place. Greptile's latest edited summary can contain actionable items even when there are no new inline comments.
  • Bot comments (deploy previews, etc.) — usually informational
  • Perforce: CL description should include a clear summary, affected files rationale, and testing notes
Show full SKILL.md (336 more words)Show less
5. Categorize issues

For each issue found, categorize as:

CategoryMeaning
ActionableCode changes, test improvements, or fixes needed
InformationalVerification notes, questions, or FYIs that don't require changes
Already addressedIssues that appear to be resolved by subsequent commits
6. Report findings

Present a summary table:

AreaIssueStatusAction Needed
Status ChecksCI build failingFailingFix type error in src/api.ts
Review"Add null check" — @reviewerActionableAdd guard clause
DescriptionTODO placeholder in test planActionableFill in test plan
Review"Looks good" — @teammateInformationalNone
7. Fix issues (if requested)

If there are actionable items:

  1. Switch to the PR/MR's branch (git) or ensure files are open in the correct CL (Perforce) if not already.
  2. Ask the user if they want to fix the issues.
  3. If yes, make the fixes, then:

GitHub/GitLab: commit and push:

bash
git add <files>
git commit -m "address review feedback"
git push

Perforce: open files for edit, make changes, and re-shelve:

bash
p4 edit <file>
# make changes
p4 shelve -f -c <CL_NUMBER>
8. Resolve review threads

After addressing comments, resolve the corresponding review threads.

Perforce — Perforce does not have a native "resolve thread" concept. Instead, mark comments as addressed by updating the CL description or by responding in the review tool being used (Swarm, etc.). If using p4 review:

bash
# Mark files as reviewed after addressing feedback
p4 review -c <CL_NUMBER>

GitHub — fetch unresolved thread IDs (paginate if needed — see the GraphQL reference):

bash
gh api graphql -f query='
query($cursor: String) {
  repository(owner: "OWNER", name: "REPO") {
    pullRequest(number: PR_NUMBER) {
      reviewThreads(first: 100, after: $cursor) {
        pageInfo { hasNextPage endCursor }
        nodes {
          id
          isResolved
          comments(first: 1) {
            nodes { body path }
          }
        }
      }
    }
  }
}'

If hasNextPage is true, repeat with -f cursor=ENDCURSOR to get remaining threads.

Then resolve threads that have been addressed or are informational:

bash
gh api graphql -f query='
mutation {
  resolveReviewThread(input: {threadId: "THREAD_ID"}) {
    thread { isResolved }
  }
}'

Batch multiple resolutions into a single mutation using aliases (t1, t2, etc.).

GitLab — fetch unresolved discussions (see the GitLab API reference):

bash
glab api "projects/:fullpath/merge_requests/<MR_IID>/discussions?per_page=100"

Filter for discussions where "resolved": false. Collect each discussion's id.

Resolve each discussion individually (GitLab has no batch resolution):

bash
glab api --method PUT \
  "projects/:fullpath/merge_requests/<MR_IID>/discussions/<DISCUSSION_ID>" \
  --field resolved=true

Repeat for each unresolved discussion ID.

9. Multiple PRs/MRs/CLs

If checking a chain of PRs/MRs/CLs, process them sequentially.

Perforce — to check multiple changelists at once:

bash
p4 changes -s pending -u $P4USER -c $P4CLIENT -l

Output format

Summarize:

  • PR/MR/CL title or description and current state
  • Platform detected (GitHub / GitLab / Perforce)
  • Status checks summary (passing/failing/pending) — or N/A for Perforce
  • Total issues found
  • Actionable items with descriptions
  • Items that can be ignored with reasons
  • Recommended next steps

© onyx-dot-app, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in .agents/skills/greptile/check-pr of onyx-dot-app/onyx.

  • SKILL.md
  • references/gitlab-api.md
  • references/graphql-queries.md

Open the folder on GitHubat commit d83b611

Used in 3 other repositories

We found 3 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in onyx-dot-app/onyx, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Check PR next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Check PR compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Check PR this skillonyx-dot-app/onyx32k2 repos~2.3kAutomated safety check: PassMIT
Visual Reviewai-dynamo/dynamo8.3k—~4.5kAutomated safety check: PassApache-2.0
Greploop Appsmichaelshimeles/skills1.3k1 repos~3.6kAutomated safety check: PassMIT
Check PRpaperclipai/paperclip99k—~3.6kAutomated safety check: PassMIT
MR and PR Description Draftertabler/tabler42k—~2kAutomated safety check: PassMIT
Plannotator Referencebacknotprop/plannotator9.2k—~6.3kAutomated safety check: WarnApache-2.0

Similar skills

  • Visual Review

    ai-dynamo/dynamo

    Create self-contained interactive HTML code-review dashboards from GitHub or GitLab pull requests, checked-out branch diffs, or supplied unified diffs, with correctness and safe-to-merge scores…

    8.3k GitHub stars~4.5k tokensUpdated today
    DevelopmentAuto-check passed
  • Greploop Apps

    michaelshimeles/skills

    Loops on a large pull request, merge request or Perforce changelist, fixing Greptile findings until it scores 5/5 with no unresolved comments.

    1.3k GitHub starsUsed in 1 repo~3.6k tokens
    DevelopmentAuto-check passed
  • Check PR

    paperclipai/paperclip

    Check a GitHub, GitLab, or Perforce PR/MR/CL for review comments, failing checks, and PR-body gaps.

    99k GitHub stars~3.6k tokensUpdated today
    DevelopmentAuto-check passed
  • Drafts a merge request or pull request title and body in simple English from the branch's git history and diff against origin/dev, ready to paste into GitLab or GitHub.

    42k GitHub stars~2k tokensUpdated today
    DevelopmentAuto-check passed
  • Plannotator Reference

    backnotprop/plannotator

    Reference for picking the right Plannotator tool or command for plan review, code review, annotating files and URLs, archived plan decisions and Guided Reviews.

    9.2k GitHub stars~6.3k tokensUpdated today
    DevelopmentAuto-check: warnings
  • Create PR

    yonatangross/orchestkit

    Creates GitHub pull requests with pre-flight validation, conventional title formatting, and structured summary generation.

    290 GitHub stars~4.5k tokensUpdated today
    DevelopmentAuto-check: notes

More from onyx-dot-app/onyx

All 9 skills in this repo
  • Greploop

    onyx-dot-app/onyx

    Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.

    32k GitHub starsUsed in 4 repos~3.3k tokens
    Auto-check passed
  • Merge Dependabot PRs

    onyx-dot-app/onyx

    Triages and lands a batch of open Dependabot PRs in the Onyx repo, where main is gated exclusively by GitHub's merge queue: approves and enqueues green PRs, closes superseded duplicates, fixes…

    32k GitHub starsUsed in 1 repo~2.2k tokens
    Auto-check passed
  • Image Generation

    onyx-dot-app/onyx

    Generate or edit raster images (photos, illustrations, textures, sprites, mockups, logos, infographics) using the workspace's configured image-generation provider via onyx-cli image.

    32k GitHub starsUsed in 1 repo~1.7k tokens
    Auto-check passed
  • Onyx CLI

    onyx-dot-app/onyx

    Query the Onyx knowledge base using the onyx-cli command. An agent skill from onyx-dot-app/onyx.

    32k GitHub starsUsed in 1 repo~2.6k tokens
    Auto-check passed
  • Playwright E2E Tests

    onyx-dot-app/onyx

    Write and maintain Playwright end-to-end tests for the Onyx application.

    32k GitHub starsUsed in 1 repo~2.8k tokens
    Auto-check: notes
  • Browser

    onyx-dot-app/onyx

    Core browser usage guide. An agent skill from onyx-dot-app/onyx.

    32k GitHub starsUsed in 1 repo~21k tokens
    Auto-check: warnings

Works with

Categories

Questions about Check PR

What does Check PR do?

Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions. Check PR is an agent skill from onyx-dot-app/onyx. Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.

When should I use Check PR?

Check PR fits situations like: the user wants to check a PR/MR/CL; address review feedback; prepare a change for submission.

How do I install Check PR in Claude Code?

Run `npx skills add onyx-dot-app/onyx --skill check-pr -a claude-code`. Or copy the skill folder (.agents/skills/greptile/check-pr in onyx-dot-app/onyx) into .claude/skills/check-pr in your project. Claude Code loads it when a task matches its description.

How do I install Check PR in Codex?

Run `npx skills add onyx-dot-app/onyx --skill check-pr -a codex`. Or copy the skill folder (.agents/skills/greptile/check-pr in onyx-dot-app/onyx) into .agents/skills/check-pr in your project. Codex loads it when a task matches its description.

Can I use Check PR in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add onyx-dot-app/onyx --skill check-pr -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/check-pr, .gemini/skills/check-pr, .github/skills/check-pr and .opencode/skills/check-pr in your project.

What does Check PR need to run?

Going by SKILL.md and its folder, Check PR needs the command-line tools its instructions call (gh, glab, git and jq). Its frontmatter pre-approves these tools: Bash(gh:*), Bash(glab:*), Bash(git:*), Bash(p4:*). Compatibility (from SKILL.md): Requires git and gh (GitHub CLI), glab (GitLab CLI), or p4 (Perforce CLI) installed and authenticated..

Does Check PR access the network?

SKILL.md contains no URLs. Its commands use gh and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Check PR safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Check PR use?

Check PR is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Check PR use?

About 2.3k tokens (SKILL.md is roughly 9.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.1k tokens, read only when the agent opens those files.

What are the alternatives to Check PR?

Skills that share tags, products or a category with Check PR: Visual Review (ai-dynamo/dynamo, 8.3k stars), Greploop Apps (michaelshimeles/skills, 1.3k stars), Check PR (paperclipai/paperclip, 99k stars) and MR and PR Description Drafter (tabler/tabler, 42k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Check PR?

onyx-dot-app (a GitHub organization) maintains it in onyx-dot-app/onyx, which has 32,364 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 9, 2026.

Source: onyx-dot-app/onyx on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.