domains / families / software-engineering / ralph-review-trio

ralph-review-trio

separate

Run a sequential three-tier code review on a finished implementation branch — Haiku (surface) → Sonnet (logic) → Opus (deep). Restarts from Tier 1 on any tier failure. Use when a solo branch or PR is code-complete and you want structured pre-merge verification before human review.

When to use

• code-complete feature or solo branch
• pre-merge verification before human review
• structured evidence of tier checklists
• implementation with satisfied acceptance criteria

When not to use

• work-in-progress branches mid-implementation
• documentation-only diffs with no code
• hotfix branches where speed dominates verification

Skill page

Source