What problem does it solve? Reviewing a branch or PR requires checking two independent questions at once: does the code follow the repo's documented standards, and does it actually implement what the 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 without merging or reranking. - Fowler smell baseline: Applies a fixed set of code smells from Refactoring ch.3 (Duplicated Code, Feature Envy, Shotgun Surgery, etc.) even when the repo documents no standards, with documented repo rules always overriding the baseline. - Spec traceability: Locates the originating spec via issue references in commit messages, a user-supplied path, or files under docs/, specs/, or .scratch/, and quotes spec lines for each finding. - Use Case: Before merging a feature branch, ask for a review since main; the skill diffs against the merge-base, checks the diff against CODING_STANDARDS.md and the linked issue, and reports violations and missing requirements separately. ## Quick Start Ask the assistant to review the changes since main using the anvil-code-review skill and report standards and spec findings separately.
