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. Mixing both in one review lets one axis mask the other. ## Core Features & Use Cases - Two-axis review: Runs a Standards review and a Spec review as parallel sub-agents so their contexts stay separate, then reports findings side by side. - Fowler smell baseline: Applies a fixed set of code smells from Refactoring (Duplicated Code, Feature Envy, Shotgun Surgery, and more) even when the repo documents no standards, with documented repo rules always overriding the baseline. - Spec traceability: Locates the originating spec from issue references in commit messages, a user-supplied path, or files under docs/, specs/, or .scratch/, and flags missing requirements, scope creep, and incorrect implementations. - Use Case: Before merging a feature branch, ask for a review since main and receive separate Standards and Spec reports, each with quoted evidence and a per-axis summary. ## Quick Start Ask the assistant to review the changes since main using the code-review skill, and point it at the issue or spec file if one exists.