What problem does it solve? Per-task code reviews only see one branch or diff at a time, so cross-module duplication, accumulated complexity, and naming drift go unnoticed. This Skill performs periodic whole-repo audits that catch the debt incremental reviews miss. ## Core Features & Use Cases - Two execution modes: Single mode runs one reviewer per top-level directory plus cross-scope reconciliation; team mode runs three independent full-repo reviewers with peer cross-verification and confidence tiers like [VERIFIED 3/3] and [DISPUTED]. - Five review categories: DRY, YAGNI, Simplicity & Efficiency, Refactoring Opportunities, and Consistency, each with Critical/High/Medium/Low severity ratings and file:line citations. - Automatic routing of findings: Inline fixes are handed to draft-plan and plan-review automatically, while complex fixes become GitHub issues or plans after user confirmation. - Use Case: After a long development sprint, run a team-mode audit to produce a dated report in docs/reviews/ ranking every finding by severity, then auto-generate fix plans for the simple ones. ## Quick Start Ask the assistant to run /codebase-review on the repository to audit the whole codebase and produce a severity-ranked findings report.