| name | pr-review-checklist |
| description | Use when reviewing a change against spec intent, correctness, maintainability, and test coverage. |
Purpose
Provides a systematic review checklist that validates code changes against the full traceability chain: code → tasks → plan → spec.
When to Use
Use this skill during PR review to ensure systematic coverage of all review dimensions.
Review Order
- Spec alignment — Does the change solve the intended problem as specified?
- Acceptance criteria — Are the acceptance criteria from the spec covered?
- Correctness — Are there logic errors, race conditions, or unhandled edge cases?
- Scope — Does the change stay within the planned scope — no more, no less?
- Architecture — Does it fit existing patterns and respect module boundaries?
- Test coverage — Are tests sufficient for the level of risk introduced?
- Operational readiness — Are logging, error handling, retry, and rollback considered?
Spec Traceability Check
When a spec exists (specs/[feature]/spec.md):
- Verify code implements what
tasks.md describes
- Verify tasks align with
plan.md
- Verify plan aligns with
spec.md
- Map each changed file/function to a spec requirement
- Identify requirements that have no corresponding code change
- Identify code changes that have no corresponding requirement (scope creep)
- Flag acceptance criteria that cannot be verified by existing tests
Output Format
Follow the structured report format defined in the PR Reviewer agent:
- Summary — what was reviewed, which mode (A/B), overall assessment
- Spec Traceability table — each requirement mapped to Met / Missing / Partial / Deviated
- Metrics — files changed, complexity estimate, test coverage gaps
- Findings table — severity-rated (🔴🟠🟡🔵), domain, file:line, issue, justification, suggested fix
- Recommended Actions — checkboxes separating must-fix from should-improve
- Risk Level — Low / Medium / High with one-line justification
Checklist
