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 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 must be addressed before merge. - Change Sizing and Dependency Discipline: Enforces reviewable change sizes, splitting strategies for large PRs, and per-package dependency upgrade review with changelog and lockfile inspection. - Use Case: Before merging a pull request that adds a new API endpoint, run this review 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.
