documentation-audit

Documentation audit systematically compares factual claims in your Markdown docs against actual code behavior to identify mismatches. Run the audit after code changes, during onboarding, or before release to ensure docs accurately reflect your codebase.

Yes. The audit validates API references, system architecture diagrams, and configuration documentation by cross-referencing them against your code. It identifies undocumented features, missing parameters, and outdated examples in one pass.

A documentation audit performs completeness checks across your repository, discovering undocumented features, APIs, configuration options, and architectural patterns. It flags gaps between what exists in code and what's documented in Markdown.

Run a multi-pass audit that indexes code, discovers claims in docs, extracts documentation facts, verifies accuracy against current behavior, and performs in-place repairs. The audit maintains a ledger of corrections for review.

Yes. The audit covers Markdown documentation, text-based diagrams, and repository navigation structures. It validates the accuracy and consistency of these elements alongside your code to ensure complete documentation alignment.