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 issue or spec asked for. Doing both in one pass causes one axis to mask the other, and findings get lost or reranked incorrectly. ## Core Features & Use Cases - Two-axis parallel review: Spawns separate Standards and Spec sub-agents so each review runs in isolated context, then aggregates findings side by side without merging or reranking. - Fowler smell baseline: Applies a fixed set of code smells from Refactoring (Duplicated Code, Feature Envy, Shotgun Surgery, etc.) even when the repo documents no standards, with repo standards always overriding the baseline. - 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 a report with a Standards section citing violated conventions and a Spec section listing missing requirements and scope creep. ## Quick Start Ask the assistant to review the changes since main using the code-review skill and report standards and spec findings side by side.