What problem does it solve?
Enforces a consistent, team-specific quality gate during pre-merge reviews so that architectural regressions, unhandled error paths, and deviations from agreed designs are caught before code lands.
Core Features & Use Cases
- Categorised findings: Produces Breaking (block merge), Important (must address), and Suggestions (optional) classifications for each observation.
- Implementation guide checks: Compares changes against the project's implementation guide and flags deviations as findings.
- Actionable references: Each finding references specific files, classes, methods, or lines and ends with a clear verdict: merge, merge with changes, or do not merge.
- Use Case: Use when reviewing a completed feature branch or pull request to ensure senior-level architectural judgment is consistently applied.
Quick Start
Review the provided diff or pull request using the code-review skill and return Breaking, Important, and Suggestions sections with file/line references and a final merge verdict.