obsidian-process

Batch normalize tags and frontmatter across an Obsidian vault using modular processors like TagNormalizer and FrontmatterProcessor. The toolkit applies deterministic transformations across large vaults to enforce metadata consistency and traceability.

The safest way to extract wikilinks before a vault migration is using a batch processor with dry-run support, automatic backups, and rollback on errors. This ensures link auditing occurs without risking data loss during transformations.

Yes, you can run vault analysis and metadata governance on large Obsidian vaults. The toolkit performs vault-wide analytics and applies pluggable processors to manage metadata consistency at scale for audits and migrations.

Yes, you need the yaml dependency to process frontmatter in Obsidian markdown files. The FrontmatterProcessor relies on it to parse and perform CRUD operations on YAML metadata during batch processing workflows.

If a batch processing error occurs during tag normalization, the toolkit executes an automatic rollback on errors. Combined with automatic backups, this reverts the vault to its prior state to prevent partial metadata updates.

Your Obsidian vault needs structured reporting after wikilink extraction to provide traceability during migrations and audits. The batch processor generates structured reports detailing link auditing results for metadata governance workflows.