oh-my-obsidian-setup

Initialize an Obsidian vault safely using preflight checks and dry-run summaries to preview changes. The process enforces non-destructive mutations and requires explicit user approval before applying any setup modifications to your existing files.

Attaching an existing Obsidian vault is supported with non-destructive mutations and explicit approval. The setup process uses preflight validation and dry-run planning to ensure your current vault state and data are preserved during attachment.

Git integration configures persistent vault resolution and hooks during Obsidian setup. It coordinates validation scripts and tracks vault state to ensure consistent repository access and prevent memory drift across project contexts.

Vault-state tracking manages persistent resolution pointers and Codex integration to prevent memory drift for AI assistants. It ensures consistent access to project context by maintaining an auditable record of vault setup changes.

Preflight checks are required before attaching an Obsidian vault to validate the current state and prevent unintended mutations. The setup wizard coordinates these helper scripts to ensure safe initialization and dry-run planning.

Explicit approval for vault mutations enforces a safe, auditable setup process that prevents unintended data loss. The dry-run summary provides a preview of all planned changes, requiring your confirmation before any modifications are applied.