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

  1. 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.
  2. 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.
  3. MUST sort findings by severity: blocker → major → minor → nit.
  4. MUST keep pre-existing, untouched code out of findings; list it under out-of-scope instead.
  5. MUST issue exactly one verdict: approve only when no blocker or major findings remain; request-changes whenever any blocker or major finding exists; comment only for informational reviews with no blocker or major finding. A clean review MUST use findings: - none and still provide a substantive summary and residual-risk statement.
  6. MUST state residual risk that remains even if the changeset merges as-is.

Output Contract

Default:

Installs
7
First Seen
Oct 12, 2026