What problem does it solve?
Unstructured, inconsistent code reviews often miss critical defects, become unproductive gatekeeping exercises, or fail to spread engineering knowledge across teams, leading to shipped bugs, wasted developer time, and gradually degrading codebase health.
Core Features & Use Cases
- 8-Pass Layered Review Methodology: Follow a consistent, ordered review flow from purpose/scope validation through to performance and security checks, ensuring no critical quality gates are skipped.
- Severity-Labeled Feedback Framework: Tag all review comments as blocking, suggestion, nit, or question to help authors prioritize fixes and avoid unproductive debates over minor issues.
- Merge Approval Criteria: Clear guidelines for when to approve, request changes, or block a pull request, balancing code quality with development velocity.
- Cross-Skill Integration: Connect to domain-specific skills (clean-code, security, testing, etc.) for targeted checklists when reviewing specialized code.
- Use Case: A mid-sized engineering team can adopt this Skill to standardize PR reviews across all squads, reduce post-ship critical bugs by 25%+, and cut average review cycle time by 30% by eliminating low-value nitpicks.
Quick Start
Use the code-review skill to review the attached pull request #456, following the 8-pass methodology and labeling all feedback by severity to help the author prioritize fixes.
