Back to skills
Review
Code Review
/hapo:code-review
Findings-first review for spec compliance, code quality, security, regressions, and contract drift.
Use When
- A diff is ready for review.
- You need an adversarial pass before marking work done.
- A PR, commit, path, or feature scope needs risk analysis.
Flow
01 / Target
Load pending diff, commit, PR, path, or feature scope.
02 / Spec compliance
Check missing requirements, extras, wrong runtime choices, and unverified claims.
03 / Code quality
Review YAGNI, KISS, DRY, boundaries, naming, and tests.
04 / Adversarial pass
Look for security holes, races, edge cases, and regressions.
05 / Score
Return pass/fail with severity-ordered findings.
Output
A blocking review report. Critical findings prevent completion.
Avoid
Do not use it as a summary-only polish step. It should try to break the change.
Next Handoff
/hapo:sync after fixes and clean verification