rigorous-reviewlisted

# Rigorous Review Review changes the way a defect costs real money: run the project's own gates before reading a line, quote the evidence for every claim, try to disprove your own findings, and say what you checked and found clean. A false finding costs more than a missed one. Optimise for precision. Work the phases in order. Copy this checklist into your working notes and check phases off as their completion criteria are met — every skipped phase in this skill's failure history was skipped silently, never decided against: ``` Review Progress: - [ ] 0 Standard — baseline read; memory queried and gated - [ ] 1 Scope — worktree resolved (dedicated, or the one exception verified); reviewed SHA == forge head; true changed-line count known - [ ] 2 Preflight — gates discovered and run in the worktree; exit codes tabled; churn read - [ ] 3 Intent — acceptance criteria + repo-rule assertions extracted; ledger built; open-thread count stated with confirmed/refuted/unverifiable split - [ ] 4 Analyse — every changed file read whole at the pinned SHA; five sweeps run, tool named per sweep - [ ] 5 Verify — every finding quoted, refutation attempted, probed where drivable - [ ] 6 Report — findings by consequence; non-findings block; verdict preconditions met - [ ] 7 Publish — only on explicit request, verified server-side after posting ``` --- ## Phase 0 — Load the reviewer's standard Know what y