permanent-rebuilder

To reorganize an Obsidian vault into a hub and leaf structure without breaking links, use a non-destructive dry-run restructure plan that moves files while preserving existing connections. The permanent-rebuilder skill generates this plan to safely reorganize permanent notes into 10_hub, 20_leaf, and 90_meta folders.

Standardizing frontmatter and enforcing metadata across permanent notes in Obsidian requires applying a guided template that ensures every file has a summary, created date, and status. This skill enforces required metadata and a standardized frontmatter template to maintain consistency across your knowledge base.

The best way to maintain MOC navigation graphs when restructuring an Obsidian vault is to update navigation references to reflect the reorganized hub and leaf structure. This skill updates MOC navigation graphs and references automatically after files are moved into their new taxonomy.

Yes, you can preview changes before applying moves to your Obsidian permanent folder by generating a safe dry-run restructure plan. This allows you to review exactly how files will be reorganized into the hub, leaf, and MOC taxonomy before any modifications are executed.

Yes, you need supporting Python scripts to restructure an Obsidian permanent vault. The process requires scan_permanent_notes.py, build_restructure_plan.py, and apply_restructure_plan.py to scan existing notes, generate a safe reorganization plan, and execute the non-destructive file moves.

Your Obsidian knowledge base needs a tag taxonomy and standardized permanent notes to improve findability and navigation within long-term storage. Establishing a repeatable hub, leaf, and MOC structure transforms a sprawling knowledge base into a durable, well-structured vault.