doc-accuracy-auditlisted

Use when asked to validate that a repo's READMEs and docs are accurate / up to date against the current code (not just diagrams — endpoints, ports, counts, env vars, commands, schemas, event contracts). Triggers on "validate the docs against the code", "make sure the docs are up to date", "audit the READMEs for accuracy", "are the docs still correct".
hjr15/claude-kit · ★ 0 · AI & Automation · score 76

Install: claude install-skill hjr15/claude-kit

# Documentation Accuracy Audit ## Overview Verify every factual claim in a repo's long-lived docs against the **current code**, fix the doc drift, and split out the code/config bugs the audit surfaces. Distinct from `readme-diagram-audit` (which only checks diagram coverage/convention) — this checks whether prose claims (endpoints, ports, service counts, env vars, commands, DB schema, event routing keys, file paths) still match reality. Scope to **long-lived docs that are meant to track current state**. Explicitly EXCLUDE point-in-time records — `docs/archive/`, `docs/superpowers/specs|plans/`, changelogs, and any git worktree subdirectories (`*-<ticket>/`) — those are frozen by design; "correcting" them is wrong. ## Steps ### Step 1 — Pre-flight - Confirm CWD and branch; `git fetch && git log HEAD..@{u} --oneline` — stop if origin is ahead (per cross-repo safety). - Enumerate the in-scope doc set: root `README.md`, `CLAUDE.md`, `docs/**` (minus the excludes above), every `services/*/README.md`, `apps/*/README.md`, `packages/**/README.md`, `deploy/README.md`. Filter out nested worktree dirs and caches. - Create a `KEY-n` branch before editing (tracked work). ### Step 2 — Fan out auditors by cluster Dispatch parallel read-only/general-purpose subagents, one per doc cluster (keep clusters file-disjoint so they never collide). Typical clusters: (1) root README + CLAUDE.md + index; (2) service READMEs; (3) app + package READMEs; (4) architecture + diagrams; (5) operations