review-pr · fcakyon — Claude Code skill: review pull requests
The review-pr skill checks pull requests for bugs, regressions, risky changes, and missing tests. Use it to get a focused list of issues before approving a PR.
Apache-2.0 ★ 1,216 updated 2026-11-02
/plugin marketplace add fcakyon/claude-codex-settings
/plugin install github-dev@claude-settingsWhat review-pr does
Give the skill a PR number or URL. If you provide neither, it tries to identify the pull request from the current branch with gh pr view --json number,headRefName. It then reads the diff and changed-file list using gh pr diff and gh pr view <number> --json files, skipping generated and vendored files.
When subagents are available, the skill delegates the review to github-dev:pr-reviewer; otherwise it follows the manual process. It reports issues in changed code, groups findings that share a cause, and orders them by severity. Comments stay pending. The skill does not submit a review automatically.
Manual review uses GitHub CLI gh and access to the PR. With no findings, the result is APPROVE - No fixes required; findings come with file references and a NEEDS_CHANGES recommendation.
What it helps with
- find bugs and regressions in a pull request
- spot risky changes and security issues
- identify tests missing from a PR
- keep pre-existing issues out of a change review
Example prompts for the agent
- Use
review-prto check this pull request for bugs and regressions. - Review the PR from the current branch and group related findings.
- Check this PR for risky changes and missing tests without submitting the review.
How to install review-pr
1Plugin marketplace
/plugin marketplace add fcakyon/claude-codex-settings/plugin install github-dev@claude-settingsThis installs the whole github-dev plugin with all its skills
2Skills CLI (Vercel)
npx skills add fcakyon/claude-codex-settings --skill review-pr -a claude-code3Manually: put the files in place
~/.claude/skills/review-pr/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/review-pr/
1Skills CLI (Vercel)
npx skills add fcakyon/claude-codex-settings --skill review-pr -a codex2Manually: put the files in place
.agents/skills/review-pr/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add fcakyon/claude-codex-settings --skill review-pr -a cursor2Manually: put the files in place
.cursor/skills/review-pr/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install fcakyon/claude-codex-settings plugins/github-dev/skills/review-pr2Manually: put the files in place
.github/skills/review-pr/SKILL.md1Skills CLI (Vercel)
npx skills add fcakyon/claude-codex-settings --skill review-pr -a gemini-cli2Platform CLI
gemini skills install https://github.com/fcakyon/claude-codex-settings --path plugins/github-dev/skills/review-prManually: put the files in place
.devin/skills/review-pr/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about review-pr
How do I install review-pr in Claude Code?
Add the marketplace with /plugin marketplace add fcakyon/claude-codex-settings, then install the plugin with /plugin install github-dev@claude-settings.
What does the review-pr skill do?
It checks pull request changes for bugs, regressions, security issues, risky changes, and missing tests. Its findings focus on issues that need fixes.
Does review-pr submit comments to the pull request?
No. It creates pending PR comments and does not submit or confirm the review automatically.
Source text
SKILL.md · Apache-2.0
--- name: review-pr description: This skill should be used when user asks to "review a PR", "review pull request", "review this pr", "code review this PR", "check PR #N", provides a GitHub PR URL, or explicitly invokes "review-pr". --- # Review PR Review a pull request for bugs, regressions, missing tests, and risky changes. When explicitly invoked with extra text, treat that text as the PR number or URL. If no PR reference is provided, infer it from the current branch. ## Process 1. **Preferred execution** - If subagents are available, use `github-dev:pr-reviewer` and pass the PR reference. - Otherwise follow the manual steps below. 2. **Parse PR reference** - If a PR number or URL is provided, extract owner, repo, and PR number. - If not, auto-detect the PR from the current branch with `gh pr view --json number,headRefName`. 3. **Fetch PR data** - Use `gh pr diff <number>` for the full diff. - Use `gh pr view <number> --json files` for the changed file list. - Skip generated or vendored files such as `.lock`, `.min.js`, `.min.css`, `dist/`, `build/`, `vendor/`, `node_modules/`, `_pb2.py`, and images. 4. **Review focus** - Only report issues that require fixes. - Only review PR changes, never pre-existing issues in unchanged code. - Prioritize bugs, security issues, breaking changes, performance issues, edge cases, and missing tests. - Combine related issues that share the same root cause. - Keep the list short and high signal. 5. **Review comment rules** - Only create pending PR comments, never submit or confirm the review automatically. - Use `gh` for GitHub operations. - Start comments in lowercase, keep them short, avoid end punctuation when possible. - Use simple language for both bot-facing and human-facing comments. ## Output Format If issues are found, report them in descending severity with file references and a final recommendation of `NEEDS_CHANGES`. If no issues are found, return `APPROVE - No fixes required`.
© Fatih C. Akyon · Apache-2.0 · fcakyon/claude-codex-settings
Similar skills
All skills for Code review and refactoring →review-pr by other authors comes first.