What problem does it solve? Code merged without structured review accumulates correctness bugs, security vulnerabilities, architectural drift, and unreadable logic. This Skill enforces a consistent multi-axis review gate so every change is evaluated against the same quality standard before entering the main branch. ## Core Features & Use Cases - Five-Axis Review: Evaluates every change across correctness, readability, architecture, security, and performance with concrete checklists per axis. - Severity-Labeled Feedback: Categorizes findings as Critical, Required, Nit, Optional, or FYI so authors know exactly what blocks merge. - Change Sizing and Splitting: Provides thresholds (~100/~300/~1000 lines) and splitting strategies (stack, by file group, horizontal, vertical) for oversized changes. - Dependency Discipline: Covers changelog review, one-package-per-change upgrades, lockfile diff review, and audit triage for dependency updates. - Use Case: Before merging a pull request, run the review checklist to verify tests, flag an N+1 query as Required, propose a structural remedy for a misplaced conditional, and approve only when the change improves overall code health. ## Quick Start Review this pull request across correctness, readability, architecture, security, and performance, and label each finding by severity.
