docs-consistency

# Docs Review > Cross-cutting documentation review that checks **consistency, accuracy, and completeness** across the entire documentation ecosystem. It verifies that docs agree with each other and with reality; installed per-repository audit or sync workflows can deepen the check but are not required. ## When to Use - After adding, removing, or renaming skills, hooks, agents, or rules - After major infrastructure changes (consolidation, new repos, renamed components) - Before publishing or sharing the public repo - Periodic health check (monthly) - When the user says "review docs", "check my docs", "are my docs consistent" ## When NOT to Use - For per-repo prose quality — use an installed repository-documentation audit if available - For mechanical count/freshness sync — use the repository's documented sync command - For code architecture — use an installed external/code audit workflow ## Argument Parsing Parse `$ARGUMENTS` for scope (optional, default `all`): | Scope | What it covers | |-------|---------------| | `all` | All 5 checks below | | `private` | Checks 1-3 on private docs only | | `public` | Checks 1-3 on public docs only | | `cross-check` | Check 4 only (public-private consistency) | | `user-manual` | Check 5 only (user manual alignment) | ## Checks ### Check 1: Count Consistency Count actual components on disk, then verify every document that states counts matches reality. **Disk counts** (source of truth): ``` Skills: find skills -name SKILL.md -t...