review
Independently review an implemented change against its requirements, risks, scope, and verification evidence.
SKILL.mdskills/review/SKILL.md
GitHubReview
Review is an evidence-based completion gate performed independently from implementation.
Stages
- Read the approved proposal, requirement deltas, tasks, and stated verification results.
- Inspect the actual diff and surrounding code, including callers and consumers.
- Check requirement coverage, edge/failure states, compatibility, security, permissions, data handling, accessibility, performance, and scope.
- Verify important claims with fresh tests, inspection, or direct probes. Treat agent reports as claims, not evidence.
- Classify findings as blocking, actionable, advisory, or accepted risk.
- Return precise findings with path/line, impact, rationale, and verification recipe.
- Approve only when blocking findings are resolved and evidence supports the completion claim.
Review must not become a second implementation pass or expand the proposal without an explicit change decision.
Duplicate Calls
Before repeating an identical tool call, defined as the same tool name with the same input, require at least one of these conditions:
- the input changed;
- the prior call failed; or
- the prior output is missing.
Every repeated call must carry a one-line reason stating which condition applies and what new evidence the call is expected to produce. An unchanged successful call with available output is not a review step.