flowing-abyss/obsidian-vault-skills/vault-check

Vault check

vault below stands for python3 .claude/_engine/vault.py, run from the vault root. Every command here only reads.

What the sections mean

• Manifests: broken YAML, keys the engine does not know, an enforce_folder that does not exist. These affect every note of the type, so report them first.
• Sources: a JavaScript source in a manifest the engine cannot answer. That field is checked only in part.
• Templates: a template.md whose properties differ from its manifest. New notes made by hand in Obsidian start out incomplete.
• Notes: findings per note. Errors are wrong data. Warnings are usually old notes that predate a rule.
• Broken links in note bodies: often planned notes that were never written. Not always a mistake.

How to work

1. Run the overview. Do not print the full audit into the conversation; it is long. Narrow with --rule, --folder, --errors.
2. Report in the user's language: what is wrong, how many, the few worst examples, and what you suggest. Group by cause, not by file. Many identical findings point at a manifest or an unfinished migration, not at the notes.
3. Change nothing until the user says what to fix. Then:

• mechanical items marked fixable: vault fix "note";
• a wrong value: vault set "note" key=value;
• manifests, templates and categories are protected zones. Propose the exact edit and wait for approval.

1. After fixes, run the same audit command again and report the difference.