cli-audit-doclisted

> **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 Doc — Documentation Quality Index (DQI) > "Stale docs are worse than no docs." — Docs-as-Tests methodology ## Core Principles 1. **Evidence-based** — every finding needs a `file:line` reference 2. **Read the code** — verify docs match implementation. Stale docs are the #1 problem 3. **Diataxis-aware** — classify each doc by type (tutorial, how-to, reference, explanation) and check mode purity 4. **Language-specific** — apply each language's idiomatic doc conventions (see `reference.md` for language-specific rules) 5. **Public API first** — public items are priority. Private items are nice-to-have 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/` (or project root) broadly (sample 15-20 key files) First, detect the primary language(s) from file extensions. Consult `reference.md` for langua