wiki-lint

To audit wiki documentation for structural integrity, use an automated linting skill that scans pages for contradictions, stale claims, and broken references without modifying content. It generates a triage report categorizing findings by severity.

Wiki rot occurs when documentation becomes disorganized, contradictory, or disconnected over time. Prevent it by running regular automated health checks that audit provenance and structural integrity to maintain a reliable source of truth.

No, the wiki audit process does not modify your existing knowledge management pages. It requires only read-only access to wiki search and page reading tools to analyze content and generate reports on documentation health.

To prioritize fixes after scanning your wiki space, review the generated triage report. It categorizes documentation issues like broken links and stale claims by severity—critical, medium, or low—helping maintainers prioritize fixes effectively.

Run a knowledge management audit after major project milestones. This ensures all new documentation is properly linked, cited, and consistent with existing concept pages, preventing contradictions and disconnected references across the wiki space.

Yes, you can use wiki-lint for ongoing maintenance of large-scale documentation trees. It applies to knowledge management workflows requiring regular maintenance, auditing wiki spaces for structural integrity, logical consistency, and provenance.