What problem does it solve? Reviewing a branch or PR requires checking two separate things — whether the code follows the repo's documented standards and whether it actually implements what the spec asked for — and mixing both in one pass lets one axis mask failures in the other. ## Core Features & Use Cases - Two-axis review: Runs a Standards review (documented repo standards plus a 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: Compares HEAD against any commit, branch, tag, or merge-base the user supplies, validating the ref and diff before spawning reviewers. - Spec discovery: Locates the originating spec from tasks/<name>/task.md, a user-supplied path, or docs/specs directories, and gracefully reports when no spec exists. - Use Case: Before merging a feature branch, ask for a review since main and receive separate Standards and Spec reports with cited violations, quoted spec lines, and a per-axis summary. ## Quick Start Ask the assistant to review the changes on this branch since main using the code-review skill.
