What problem does it solve? Code changes often get merged with superficial reviews that only check whether tests pass, letting bugs, security vulnerabilities, and architectural problems slip into the main branch. This Skill enforces a structured, multi-dimensional review process so every change is evaluated consistently before merge. ## Core Features & Use Cases - Five-Axis Review: Evaluates every change across correctness, readability, architecture, security, and performance with concrete checklists for each dimension. - Severity-Labeled Feedback: Categorizes findings as Critical, Nit, Optional, or FYI so authors know exactly what must be fixed versus what is a suggestion. - Change Sizing and Splitting Guidance: Defines target change sizes (~100 lines) and provides stacking, horizontal, and vertical splitting strategies for oversized PRs. - Use Case: Before merging a pull request, run this review to verify tests cover the change, check for N+1 queries and injection vulnerabilities, confirm the change description stands alone in version control history, and produce a verdict of approve or request changes. ## Quick Start Review the current uncommitted changes or the specified pull request across all five quality axes and produce a severity-labeled review report with a merge verdict.
