wiki-lint

To check an Obsidian vault for broken links and orphan pages, you can run a wiki audit that scans graph integrity and identifies disconnected notes. The process evaluates link validity and page isolation, producing a severity-ranked report with file paths and concrete repair actions.

Knowledge base provenance tracks the origin and source debt of information within your wiki. Auditing provenance gaps matters for wiki maintenance because it ensures durable research notes remain trustworthy, catching unreliable claims and source attribution issues before they spread into stale operating rules.

You can audit markdown frontmatter by running a structural health check that scans files for missing metadata fields. This linting process validates frontmatter consistency across the vault, generating a report that highlights files lacking required attributes and recommends specific repair actions.

Wiki linting does work for detecting contradictions and content drift in research notes by applying lifecycle awareness and statistical analysis. It evaluates stale content, identifies conflicting claims, and measures drift over time, outputting a ranked report of inconsistencies requiring human review.

You can validate a knowledge base after a large data ingest by running post-ingest validation checks for graph damage and trust issues. This process catches structural problems, frontmatter gaps, and workflow regressions introduced during the ingest, ensuring the wiki remains navigable before publishing.

The best way to find stale content in a markdown knowledge wiki is through lifecycle-aware auditing that evaluates page freshness and index mismatches. This approach identifies outdated operational rules and dormant notes, delivering a ranked report with severity levels and recommended maintenance actions.