| name | vault-doctor |
| description | vault-doctor CLI wrapper for Obsidian vault diagnostics and auto-fix. Triggers on vault health, scan vault, fix vault, check vault, frontmatter issues, tag conflicts, vault-fix, vault-scan. |
vault-doctor
Run vault-doctor CLI to diagnose and fix Obsidian vault health issues.
Trigger
- User asks about vault health, vault diagnostics, frontmatter issues, tag conflicts
- User mentions broken wikilinks, orphans, stale markers
- User says "scan vault", "fix vault", "check vault health"
- User invokes
/vault-scan or /vault-fix
Prerequisites
Install vault-doctor CLI:
npm install -g vault-doctor
Commands
Scan (diagnostics only)
vault-doctor scan .
Options:
--json — machine-readable output--format compact — TSV format (pipe-friendly)--severity high — only critical + high issues
Fix (auto-remediation)
vault-doctor fix .
Options:
--dry-run — preview without writing (only if user explicitly requests)
What gets auto-fixed
- Malformed YAML (closing
--- merged into values)
- Missing frontmatter (injects tags + created)
- Tag conflicts (removes lower-priority tag)
- Missing layer tags (
layer/raw or layer/wiki)
- Missing
created date on wiki notes
Manual-only issues
- Broken wikilinks — requires content knowledge
- Orphan files — requires editorial decision
- Stale markers — requires content review
Workflows
/vault-scan (read-only diagnostics)
- Run
vault-doctor scan . --severity medium
- Parse and report:
- Summary of all issues by severity
- Auto-fixable item count
- Top 5 manual-action items
- Recommended action priority
/vault-fix (scan + fix + verify)
- Scan:
vault-doctor scan . --json
- Fix:
vault-doctor fix .
- Verify:
vault-doctor scan . --severity high
- Report: files fixed, changes made, remaining issues
- Ask user whether to commit
Command Selection Guidelines
- Fixable issues: Use
fix directly without flags
- Non-fixable issues: Use
scan for diagnostics
- Trust the fixable attribute: If
Fixable: True, use fix directly
