What problem does it solve?
Code reviews often stop at the diff, miss affected surrounding code, and produce vague or low-confidence findings. This Skill enforces a disciplined review process that maps the full affected corridor, builds a QA coverage ledger, triages findings by evidence and root cause, and issues clear advisory, boundary, or ship verdicts.
Core Features & Use Cases
- Multi-target review orchestration: Review sessions, worktrees, commits, branches, PRs, features, plans, or release readiness with explicit change basis and affected-corridor analysis.
- Structured QA coverage: Enumerate material behavior dimensions (success, failure, retry, persistence, compatibility, platform) and record PASS/FAIL/BLOCKED dispositions with evidence.
- Finding triage and fix loops: Classify findings by claim, impact, response, and authority; optionally execute authorized root-cause fixes and re-review the changed corridor.
- Use Case: Before merging a large feature branch, ask for a boundary review. The Skill inventories the change basis, delegates independent review lanes, runs QA scenarios, deduplicates findings by root cause, and produces a verdict with residual risks and exact next actions.
Quick Start
Use the happier-review skill to perform a boundary review of the current branch against its plan, including QA coverage and a merge-readiness verdict.
