Agent skill · software engineering · paperclipai
check-pr
Check 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.
Why this skill is useful
Adds executable scripts for analyzing PRs/MRs/CLs across multiple platforms with specific commands that aren't commonly known.
What it needs
Requires gh, git, glab, p4 installed locally. About 8k tokens when loaded. Last updated 2026-08-07. 75,771 stars on the source repository.
What this skill does
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: 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: GitLab: Perforce: Key field differences between platforms: GitHub: number, headRefName, headRefOid GitLab: iid, sourcebranch, sha Perforce: changelist number (CL), shelved files for in-review CLs 2. Fetch PR/MR/CL details GitHub: 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 updatedat, including any "Prompt to fix all with AI" section, before concluding that the PR is clear. GitLab: For GitLab, paginate discussions if needed (add ?perpage=100&page=N). Perforce: 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 INPROGRESS (GitHub) / running or pending (GitLab), poll every 30 seconds until all checks reach a terminal state. GitHub: poll statusCheckRollup from gh pr view. GitLab: Pipeline statuses: running, pending, success, failed, canceled, skipped. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills paperclipai/check-pr