vault-doctor

To find and fix broken backlinks and orphaned notes in an Obsidian vault, run a health check to audit vault integrity. This diagnostic process surfaces stale links and mismatched metadata in a safe dry-run report before applying repairs.

Yes, you can scan and repair vault integrity issues safely because the audit runs in dry-run mode by default. This reports broken backlinks and inconsistent metadata via JSON without modifying files until you explicitly invoke repair commands.

You can scope Obsidian vault health checks to a specific project folder by invoking the diagnostic tool with project filters. This restricts the integrity audit and subsequent repair workflows to only the notes and backlinks within that defined project scope.

The best way to automate repairing inconsistent metadata across Obsidian notes is to run an automated health check battery that detects integrity problems. You can then interactively apply targeted repairs per-project after reviewing the initial diagnostic report.

Yes, you need Python installed to run automated vault diagnostics and repairs. The audit requires a Python-based dispatcher and modular check scripts to execute its battery of health checks and generate JSON reports for interactive fixing.

Your Obsidian vault still shows stale links after a diagnostic dry-run because dry-run mode only audits and reports integrity problems without modifying files. You must explicitly trigger the repair workflow to apply the suggested fixes to the broken backlinks.