daily-obsidian-vault-commit

You can automate daily git commits for an Obsidian vault by running a scheduled routine that stages all markdown changes and commits them to the main branch. It validates the current branch, inspects staged changes, and generates an agent-readable commit message.

Yes, the daily Obsidian vault commit process updates the knowledge graph by triggering a best-effort graphify update step after committing markdown changes. This ensures your vault's knowledge graph reflects the latest versioned snapshot.

If there are no markdown changes in the Obsidian vault during the daily commit, the routine performs a no-op exit on a clean working tree. It avoids creating empty commits and safely stops without automatically checking out other branches.

No, you cannot run the Obsidian vault snapshot routine on a branch other than main because it requires strict branch validation. The automated commit process stops if it detects you are not on the main branch to ensure safe versioning.

The automated vault commit handles git write operations using sandbox-aware handling for .git directories and formats commit messages with a mandatory [auto] prefix and Routine trailer. This ensures commits are agent-readable and clearly identified as automated routines.