What problem does it solve? Code reviews often drift into personal taste, style nits, or rubber-stamping because tests pass, while unmet requirements, misleading names, copied legacy residue, and ambiguous state models slip through and become expensive contracts. This Skill enforces an objective, evidence-based review that surfaces material concerns in priority order without issuing merge verdicts. ## Core Features & Use Cases - Requirement-first review: Triangulates the change's contract from tickets, acceptance criteria, tests, and repository conventions before judging implementation, then checks correctness, design integrity, scope, risk, project fit, non-functional obligations, and regression protection in a fixed order. - Structural defect classification: Identifies and classifies semantic integrity, copy-residue, state-model, boundary/ownership, representation-mismatch, and change-amplification defects with mismatch, invariant, amplification, and corrective direction. - Advisory output format: Produces a structured review assessment with at most five prioritized findings across material concerns, questions, and worth-considering sections, never an approve/reject verdict. - Use Case: When reviewing a PR that adds a greenfield OrdersV3Controller copied from another service with no V1 or V2, the Skill flags the false version history as a material semantic-integrity defect and recommends renaming to an unversioned controller. ## Quick Start Review this pull request for unmet requirements, structural design defects, scope discipline, and missing regression tests, and return prioritized material concerns without a merge verdict.
