fcakyon/claude-codex-settings / plugins/github-dev/skills/review-pr
review-pr
VerifiedThis skill should be used when user asks to "review a PR", "review pull request", "review this pr", "code review this PR", "check 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
-
Preferred execution
- If subagents are available, use
github-dev:pr-reviewerand pass the PR reference. - Otherwise follow the manual steps below.
- If subagents are available, use
-
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.
-
Fetch PR data
- Use
gh pr diff <number>for the full diff. - Use
gh pr view <number> --json filesfor 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.
- Use
-
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.
-
Review comment rules
- Only create pending PR comments, never submit or confirm the review automatically.
- Use
ghfor 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.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 466k | Updated | Claude CodeCodex | Verified | Install |
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 466k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |