What problem does it solve? Reviewing a branch or PR requires checking two separate things at once: whether the code follows the repo's coding standards and whether it actually implements what the issue or spec asked for. Mixing both in one review lets one axis mask the other, so problems slip through. ## Core Features & Use Cases - Two-axis review: Runs a Standards review (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: 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 issue references in commit messages, a user-provided path, 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. ## Quick Start Ask the assistant to review the changes on this branch since main using the code-review skill.
