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 gates 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 exactly what must be addressed before merge. - Change Sizing and Splitting Guidance: Defines thresholds for reviewable change sizes and provides strategies (stacking, horizontal, vertical) for splitting oversized PRs. - Use Case: Before merging a pull request that adds a new API endpoint, run this review to verify edge-case handling, check for N+1 queries and injection risks, confirm tests cover the behavior, and produce a structured verdict of approve or request changes. ## Quick Start Review this pull request across correctness, readability, architecture, security, and performance, and give me severity-labeled findings with an approve or request-changes verdict.
