audit-docs

You can audit planning documentation for staleness by validating the presence and cross-document consistency of core files like CLAUDE.md, .planning, and CI references. The audit detects untracked or outdated sections and generates a concise risk report with recommended fixes.

Before a Git commit, check for uncommitted changes, missing core docs, and incomplete project-structure entries. Validating cross-document consistency across CLAUDE.md and CI references highlights onboarding and review issues to fix prior to committing.

To detect stale docs in CLAUDE.md and .planning directories, run an audit workflow that verifies file paths, scans Git history, and enforces cross-document consistency. This surfaces outdated sections and context window bloat affecting current guidance.

Yes, the documentation audit checks CI references and testing guides by validating the presence and consistency of files like .github/CI.md and tests/TESTING.md. It detects missing entries that affect onboarding and code reviews.

The best way to verify project-structure completeness is to run an audit that checks file path verification and enforces the presence of core documentation. This identifies missing entries and context bloat before they affect development guidance.

Context window bloat happens in planning documentation when outdated sections and untracked entries accumulate across CLAUDE.md and .planning files. Auditing these docs for staleness and gaps ensures current, actionable guidance without unnecessary overhead.