audit-documentation

You can audit markdown documentation for consistency by scanning all tracked files to validate static accuracy, verify claim references, and generate a structured report with actionable fixes.

Cross-document consistency checking validates claims and references across tracked markdown files to ensure factual alignment and confirm that file existence and external references remain up to date.

Validating documentation claims against repository evidence involves scanning tracked markdown files to check static accuracy and verify that referenced files and cross-document claims match actual repository contents.

Yes, running a static analysis audit on tracked markdown files produces a structured report with actionable fixes, written to a temporary run-specific markdown file in the agent layer directory.

The best way to find broken references and inaccuracies is to inventory tracked markdown files and apply static validation to surface inconsistencies, generating a report with suggested fixes.

The audit applies to all tracked markdown files and configured scopes, ensuring that static validation and cross-document consistency checks cover the relevant repository documentation.