wiki-doctor

To detect documentation drift, audit wiki consistency by verifying claims against the current codebase. This process surfaces stale references, coverage gaps, and structural drift across project-wide documentation to eliminate documentation rot.

Automated wiki linting is a multi-round, adversarial audit of wiki structure, frontmatter, and link integrity. You need it before major releases to ensure architectural claims remain accurate and no documentation pages have become orphaned or contradictory.

Check for orphaned or contradictory documentation by running an automated health audit across project-wide documentation. This multi-round validation identifies coverage gaps, stale references, and structural drift between your wiki and codebase.

Yes, you can audit wiki frontmatter and link integrity without manual review by using automated linting. This performs iterative, multi-round validation and reporting to diagnose documentation health and surface structural inconsistencies.

Yes, performing iterative documentation health audits requires integration with doc-linter and wiki-differ agents. These dependencies enable the multi-round validation and reporting needed to verify wiki claims against the codebase.

The best way to ensure documentation accuracy before a major release is running an automated health audit to verify all architectural claims in the wiki are still accurate and identify any documentation that has drifted from the codebase reality.