wiki-lint

To find orphaned pages and broken wikilinks in an Obsidian vault, run a wiki lint audit that counts incoming wikilinks per page and validates internal link targets. This produces a structured health report flagging isolated notes and missing references.

Checking Obsidian frontmatter for missing required fields and summaries requires scanning each note's metadata block. A wiki lint tool applies frontmatter-scoped greps to validate necessary fields and flag absent or excessively long summaries for remediation.

Detecting stale content and provenance drift in a knowledge base involves comparing page update timestamps against source files and computing extracted or inferred fractions. This analysis flags unsourced synthesis and notes needing synchronization with their origins.

Yes, you can verify index.md consistency and measure tag cohesion in a large Obsidian wiki by running periodic quality checks. The audit reads index and log files to detect mismatches and identifies fragmented tag clusters for structural repair.

Yes, wiki lint supports automated fixes for fragmented tag clusters and index mismatches. After producing a structured health report, it offers user-approved or automatic remediation to append lint results to log.md and resolve structural metadata issues.

You should run an Obsidian wiki health check during an ingestion pipeline when adding new content or performing routine maintenance on large vaults. This prevents structural degradation by catching broken links, missing frontmatter, and provenance drift early.