cli-audit-codelisted

> **Optimization:** This skill uses on-demand loading. Heavy content lives in `references/` and is loaded only when needed. > **Language rule:** Skill instructions are written in English. When generating user-facing output, detect the project's primary language (from README, comments, docs, commit messages) and produce the report in that language. If the project is bilingual, ask the user which language to use before proceeding. # Audit Code — Code Quality Index (CQI) > "Complexity is the single greatest enemy of reliability." — John Ousterhout ## Core Principles 1. **Evidence-based** — every finding needs a `file:line` reference. No vague "the code could be better" 2. **Proportional** — a 200-line function matters more than a missing doc comment. Scale to project type 3. **Language-aware** — detect the project language and apply its idiomatic patterns, not Java/C# defaults 4. **Named anti-patterns** — use Fowler/Mantyla taxonomy names (Feature Envy, Shotgun Surgery) in findings 5. **Positive reinforcement** — always highlight good practices found, not just violations 6. **Gotchas** — read `../../gotchas.md` before producing output to avoid known mistakes ## Input `$ARGUMENTS` is the target to audit (file path, directory, or empty for whole `src/`). - If a specific file: audit that file deeply - If a directory: audit all source files in it - If empty: audit `src/` broadly (sample 15-20 key files) ## 12-Dimension Framework Score each dimension **0.0-1.0**, then compu