7. Utility Commands
Forge includes a small set of utility commands that support specialized maintenance workflows outside the main schema, lint, repair, export, and shape systems.
These commands are intentionally separated from the core workflows because they perform targeted operational tasks rather than general vault maintenance.
Rename Dataview Folder
Run:
Forge: Rename Dataview Folder
This utility helps update Dataview folder references after folder renames or vault reorganizations.
Folder-based Dataview queries can become fragile when folders move or get renamed.
This command exists to help reduce the cleanup work after structural changes.
Typical use cases:
- reorganizing project folders
- renaming operational areas
- splitting large vault sections
- restructuring PARA-style layouts
- consolidating old folder hierarchies
Why This Is Separate
Folder renames are content operations.
They are different from:
- linting
- retention cleanup
- metadata normalization
- report maintenance
Because of that, Forge keeps rename utilities separate from the normal maintenance workflow.
This helps reduce accidental large-scale structural changes during routine cleanup tasks.
Recommended Workflow
Before running any folder rename utility:
- Make sure the vault is backed up or versioned
- Run Vault Lint first so you have a clean before-state report
- Perform the rename operation
- Re-run Vault Lint afterward
- Review Dataview dashboards and queries
This makes it easier to identify:
- broken folder references
- stale links
- outdated dashboards
- missed query paths
Dataview and Structural Consistency
Dataview workflows often depend on predictable folder structures.
Examples:
FROM "Projects"
FROM "Areas/Research"
FROM "Clients/Active"
When folders move, those queries may stop returning expected notes.
Rename utilities help reduce the amount of manual cleanup required afterward.
Recommended Caution
Large folder reorganizations can affect:
- Dataview queries
- dashboards
- templates
- exports
- automation workflows
- linked operational systems
For larger vault changes:
- use Git if possible
- make incremental changes
- validate exports afterward
- review dashboards carefully
Slow migrations are usually safer than giant one-shot reorganizations.
Why Utility Commands Stay Small
Forge intentionally keeps utility commands limited and focused.
The core Forge workflows are:
- schemas
- linting
- normalization
- repair
- patches
- exports
- shapes
Utility commands exist to support edge workflows without turning Forge into a giant vault automation framework.
