What problem does it solve?
Standardizes and enforces thorough reviews so code changes do not introduce correctness, readability, architectural, security, or performance regressions before merging. It prevents unreviewed or poorly reviewed changes from degrading code health and ensures verification is documented.
Core Features & Use Cases
- Five-axis review covering correctness, readability & simplicity, architecture, security, and performance to give a holistic assessment of each change.
- Checklist-driven workflow with severity-labeled findings (Critical, Required, Optional/Nit) and explicit verification steps to close the loop on fixes.
- Change sizing and splitting guidance to keep reviews fast and focused, plus a multi-model review pattern for AI-assisted development.
- Use Case: Run this Skill on any pull request, refactor, bug fix, or AI-generated patch to produce prioritized review findings, remediation suggestions, and a verification story that documents tests and manual checks.
Quick Start
Run a five-axis review of the changes in PR #123 and return severity-labeled findings, a recommended verdict, and a verification checklist.