doc-alignment

To verify repository documentation matches the codebase, run an automated audit that extracts concrete claims from markdown files and validates them against source code and build configs to identify stale or incorrect documentation.

Documentation drift occurs when markdown files no longer reflect the current codebase implementation. You detect stale docs by scanning README, CONTRIBUTING, and inline documentation to validate concrete claims about paths, APIs, workflows, and configuration against source code.

Yes, you can audit markdown docs before a release to find incorrect API references and setup steps by extracting testable claims from documentation and verifying them against source code and runtime manifests to ensure contributors do not follow outdated instructions.

The best way to generate a risk-ranked mismatch report is to audit markdown documentation against the codebase, classify mismatches by severity as high, medium, or low, and provide actionable patch guidance with evidence citations for documentation updates.

Yes, this documentation audit works with standard markdown files like README and CONTRIBUTING, automatically scanning the repository for root-level markdowns and docs in standard directories like docs/ and .claude/ to validate their claims against the source code.