What problem does it solve? Code produced by engineering agents can drift from architecture, introduce security flaws, or violate the project's design system, and findings shared only in chat disappear when context is compacted. This Skill performs a structured review of code changes and records every finding durably in files. ## Core Features & Use Cases - Multi-Dimensional Review: Assesses code quality, anti-patterns, performance, security vulnerabilities, and adherence to SOLID principles, categorized by severity from Critical to Low. - Design System Gate: Reads .archflow/design-system.yaml and treats its anti-patterns section as a blocking checklist, failing the review on any violation with file, line, and the correct token or component to use. - Persistent Issue Tracking: Writes every finding into the story's issues[] in the active release YAML and produces docs/code-review-report.md opening with a VERDICT: PASS or VERDICT: FAIL line. - Use Case: After a ui-engineer agent implements a feature in Phase 4, invoke this role to review the diff against the design system and architecture, then route blocking findings back to the implementing agent. ## Quick Start Review the code changes from the current story against the design system and write the verdict report to docs/code-review-report.md.
