obsidian-vault-maintainer

To keep wikilinks and frontmatter consistent in an Obsidian vault, automated maintenance processes validate link determinism and ensure frontmatter compatibility with Dataview queries. This approach prevents broken references and dashboard rendering errors across your memory wiki.

The best way to automate non-destructive updates to a memory wiki is by probing the vault mode first and verifying Obsidian CLI availability. This allows incremental updates to be applied safely, ensuring that any handwritten notes surrounding generated sections remain untouched.

Yes, Obsidian CLI availability directly affects vault maintenance by dictating whether dedicated helpers like search, open, command, and daily can be used. The maintenance process probes the vault to verify CLI status before attempting any operational actions or incremental updates.

You verify vault mode before applying incremental updates by starting with a status check command to confirm the current vault configuration. This validation step ensures the environment is correctly set up before any non-destructive update procedures are executed.

Dataview queries fail when frontmatter is inconsistent because the plugin relies on standardized metadata fields to filter and display notes. Validating frontmatter compatibility during vault maintenance ensures that Obsidian dashboards and Dataview-style queries render correctly without missing data.

Yes, you can safely add handwritten notes around generated sections in an Obsidian memory wiki when the maintenance process keeps those sections deterministic. By validating the vault mode and using non-destructive update procedures, your manual annotations remain protected from automated overwrites.