obsidian-vault-maintainer

Maintaining Obsidian vault sync requires enforcing stable filenames and frontmatter compatibility to prevent broken wikilinks. This ensures Dataview queries and dashboards function reliably across all synced notes and devices.

Obsidian dashboards break after renaming notes because wikilinks referencing old filenames become invalid. A link-repair plan must execute before any renaming to ensure deterministic output, keeping handwritten notes and generated sections intact.

Checking Obsidian CLI availability involves probing the command-line interface before depending on it. This verifies whether the app is installed, running, or configured, preventing workflow failures when executing search, open, command, or daily note actions.

Dataview works with generated frontmatter when the vault maintenance process enforces frontmatter compatibility. This ensures queryable metadata remains consistent, allowing Obsidian dashboards and workflows to parse and display data correctly.

The best way to add handwritten notes around generated sections is to use deterministic output. This guarantees generated content remains stable and predictable, so manual additions are preserved without being overwritten during vault synchronization.

You should avoid destructive file renames in an Obsidian vault unless a link-repair plan is already in place. Without repairing wikilinks proactively, renames break cross-note navigation, corrupt Dataview queries, and damage dashboard integrity.