pr-review
Installation
SKILL.md
PR Review
Purpose
Review pull requests, diffs, and changesets. Inspect what actually changed, produce author-facing findings that are specific and actionable, and close with a verdict the author can act on.
Workflow
- MUST scope the review to the changeset: read the diff first; open surrounding files only to understand the changed lines. If the diff is unavailable or truncated, ask for it before reviewing.
- MUST verify each finding against the actual code before reporting it; if a finding cannot be confirmed from the available context, mark it as a question, not a defect.
- MUST sort findings by severity: blocker → major → minor → nit.
- MUST keep pre-existing, untouched code out of findings; list it under out-of-scope instead.
- MUST issue exactly one verdict:
approveonly when no blocker or major findings remain;request-changeswhenever any blocker or major finding exists;commentonly for informational reviews with no blocker or major finding. A clean review MUST usefindings: - noneand still provide a substantive summary and residual-risk statement. - MUST state residual risk that remains even if the changeset merges as-is.
Output Contract
Default: