What problem does it solve? Code reviews often conflate two separate questions — does the code follow the repo's standards, and does it actually implement what was asked — 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 fixed Fowler code-smell baseline) and a Spec review (requirements coverage, scope creep, wrong implementations) as parallel sub-agents, then reports them side by side. - Fixed-point diffing: Reviews changes since any commit, branch, tag, or merge-base using git diff <fixed-point>...HEAD, 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 spec files under docs/, specs/, or .scratch/. - Use Case: Before merging a feature branch, ask for a review since main — you get a Standards report citing violated conventions and possible smells, plus a Spec report quoting unmet or over-built requirements. ## Quick Start Ask the assistant to review the changes on this branch since main using the code-review skill.
