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 issue or spec asked for — and mixing both concerns in one pass causes findings to mask each other. ## Core Features & Use Cases - Two-axis review: Runs a Standards review (documented repo conventions 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: 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. - Automatic spec discovery: Locates the originating spec from issue references in commit messages, user-provided paths, 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 under 400 words, with a one-line summary of findings per axis. ## Quick Start Ask the agent to review the changes on this branch since main against the repo's coding standards and the originating issue spec.
