What problem does it solve? Code reviews often conflate two separate questions: whether code follows project conventions and whether it actually implements what was requested. This Skill reviews a complete change set since a fixed point (commit, branch, tag, or merge-base) along independent Standards and Spec axes so one axis cannot mask failures in the other. ## Core Features & Use Cases - Four-part scope capture: Collects committed diffs, staged changes, unstaged changes, and untracked files relative to a resolved merge-base, so nothing in the working tree escapes review. - Standards axis with smell baseline: Checks documented repo standards plus a fixed set of Fowler code smells (Duplicated Code, Feature Envy, Shotgun Surgery, and more), with repo standards always overriding the baseline. - Spec axis with source resolution: Locates the originating issue, PRD, or spec file (including Docs/Specs/) and reports missing requirements, scope creep, and incorrect implementations with quoted spec lines. - Use Case: Before opening a pull request, run this Skill against main to get separate ## Standards and ## Spec reports, then follow up with the repository's comprehensive review skill for merge readiness. ## Quick Start Review all changes since origin/main against the repo's coding standards and the spec for this branch.
