What problem does it solve? Reviewing a branch or PR requires checking two separate things at once: whether the code follows the repo's documented standards and whether it actually implements what the originating issue or spec asked for. Doing both in one pass causes one axis to mask the other, and findings get lost or conflated. ## 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, incorrect implementations) as parallel sub-agents, then reports them side by side. - Fixed-point diffing: Reviews the diff between HEAD and any user-supplied commit, branch, tag, or merge-base using three-dot git diff semantics. - Automatic spec discovery: Locates the originating spec from issue references in commit messages, user-provided paths, or spec 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 a per-axis summary of the worst finding. ## Quick Start Ask the assistant to review the changes on this branch since main using the code-review skill.
