What problem does it solve? Code reviews often conflate two separate questions — whether the code follows project conventions and whether it actually implements what was asked — letting one concern mask the other. This Skill separates those axes so a change that passes standards but misses the spec (or vice versa) is never silently approved. ## Core Features & Use Cases - Two-axis review: Runs a Standards review (repo-documented 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 three-dot git diff, with upfront validation that the ref resolves and the diff is non-empty. - Spec discovery: Locates the originating spec from issue references in commit messages, a user-supplied path, or files under docs/, specs/, or .scratch/. - 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, with hard violations distinguished from judgement calls. ## Quick Start Ask the assistant to review the changes on this branch since main using the code-review skill.
