What problem does it solve?
Solo developers merging their own branches lack structured pre-merge verification, so surface bugs, logic errors, and architectural drift slip through a single-pass review. This Skill enforces a layered review loop that restarts from the beginning whenever any tier fails.
Core Features & Use Cases
- Three-tier sequential review: Tier 1 (Haiku) checks surface issues like debug code and magic numbers, Tier 2 (Sonnet) traces cross-file logic and contracts, Tier 3 (Opus) audits architecture, governance drift, and factual claims.
- Restart-on-fail loop: Any tier failure triggers fixes and a full restart from Tier 1, ensuring later tiers always review the final state of the code.
- Structured RESULT blocks: Each tier emits a fenced verdict block with findings, file paths, and evidence so the controller can decide pass, restart, or merge.
- Use Case: After finishing a feature branch that adds a retry wrapper to an HTTP client, invoke the review to catch a leftover print statement at Tier 1, a swallowed exception at Tier 2, and confirm governance cadence at Tier 3 before merging.
Quick Start
Ask Claude to run /ralph-review on your completed feature branch to execute the three-tier pre-merge review.