oh-my-obsidian-vault-manager

Obsidian vault organization is automated by moving loose Markdown files into structured directories like 작업기록/세션기록. The manager plans file moves with an explicit confirmation step to ensure safe reorganization of misplaced notes.

An Obsidian vault health check summarizes vault state and Git status to validate integrity. It inspects the root-level layout to identify orphaned notes and provides actionable remediation steps for ongoing maintenance.

Adding new documents to Obsidian vault folders uses safe, relative-path placement under organized directories such as 작업기록/세션기록. You run the vault manager, choose a target folder, and the document is created there.

Obsidian vault maintenance during migrations is supported by inspecting vault structure and reorganizing files. Mutating operations are gated by setup status, and all actions stay within the resolved vault boundary to prevent data loss.

Git is not required to manage your Obsidian vault structure, but the health check flow summarizes Git status alongside vault state. Core organization and document management functions operate independently of Git.