Individual skill
pull-request-review
Review a pull request or branch diff like a staff engineer. Verify it does what the issue asks, find correctness and security defects with file and line evidence, check tests and compatibility, and deliver prioritized, actionable comments. Use for PR review, branch review, and "review my changes".
src/skills/builtin/pull-request-review/SKILL.md
Source commit 79a26efbea50aa0e351c4b5fbdfc6502fef25b8e
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 5, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 216
- Repository last updated
- Nov 5, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agentic-ai Repository topic
- ai Repository topic
- code-cli Repository topic
- code-generation Repository topic
- llms Repository topic
- ai-agents-cli Repository topic
- autonomous-agents Repository topic
- ai-coding-agent Repository topic
- ai-coding-agents Repository topic
- coding-agent Repository topic
- security Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 2,210 bytes
Read excerpt
# Review the change, not the style guide
A useful review finds the defect that would have shipped and explains it so the
author can fix it in one pass.
## Establish scope
1. Get the diff (`git_diff` for the working tree, `git_diff_range` against the
base branch). Read the whole diff before commenting on any part.
2. Read the linked issue, PR description, or commit messages. Write one line
stating what the change claims to do.
3. Open the files around the diff; a change is only correct in context.
## Check in this order