What problem does it solve? Code merged without structured review accumulates defects, security vulnerabilities, and architectural debt. This Skill enforces a consistent multi-axis review process so every change is evaluated against the same quality bar before entering the main branch. ## Core Features & Use Cases - Five-Axis Review: Evaluates every change for 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 what must be fixed versus what is optional. - Change Sizing and Splitting Guidance: Defines reviewable change sizes (~100 to ~300 lines) and provides stacking, horizontal, and vertical splitting strategies for oversized changes. - Dependency Review Discipline: Covers changelog reading, one-dependency-per-change upgrades, lockfile diff review, and audit triage. - Use Case: Before merging a pull request that adds a new API endpoint, run the review checklist to verify tests cover edge cases, inputs are validated at boundaries, no N+1 queries exist, and the change description stands alone in version control history. ## Quick Start Review this pull request across correctness, readability, architecture, security, and performance, and label each finding by severity.
