What problem does it solve? Code reviews often conflate two separate questions — does the code follow the project's conventions, and does it actually implement what was asked for — letting one axis mask failures in the other. This Skill separates them into independent parallel reviews so neither hides the other's findings. ## Core Features & Use Cases - Two-axis review: Runs a Standards review (repo conventions plus a Fowler code-smell baseline) and a Spec review (fidelity to the originating issue or spec) as parallel sub-agents, then reports them side by side. - Fixed-point diffing: Reviews changes since any commit, branch, tag, or merge-base using a three-dot git diff, with upfront validation that the ref resolves and the diff is non-empty. - Smell baseline: Applies a labelled set of Fowler code smells (Duplicated Code, Feature Envy, Shotgun Surgery, and more) as judgement-call heuristics that documented repo standards always override. - Use Case: Before merging a feature branch, ask for a review since main and receive separate Standards and Spec reports, each citing the violated rule or spec line, plus a per-axis summary. ## Quick Start Ask the assistant to review the changes on this branch since main using the code-review skill.
