Vault Cleanup Workflow: Normalize Tags and Headings (Agent Mode)

A safe Obsidian AI workflow to standardize tags, rename headings, and clean up formatting across a folder using SystemSculpt Agent Mode approvals and reviewable diffs.

Teams & OpsAdvanced25 min

Steps

1

Pick a small scope

Start with a single folder or 10 to 30 notes so you can validate the rules before scaling up.

2

Define normalization rules

Write explicit rules for tag naming, heading structure, and formatting so outputs are deterministic.

3

Run a dry proposal

Ask SystemSculpt to propose changes without writing, and review the plan for edge cases.

4

Approve changes in batches

Apply edits using Agent Mode approvals, approving only the diffs that match your rules.

5

Spot check and iterate

Open a handful of edited notes and refine the rules before expanding to more content.

Safety first

Bulk edits are where AI can hurt you if you do not use approvals. Keep Agent Mode approvals enabled and work in small batches.

Inputs (copy/paste)

Before you run cleanup, write these in your scope note:

  • Target folder: one folder or note batch you will normalize.
  • Rules: naming, tags, heading conventions, and formatting rules.
  • Do-not-change list: meaning-critical notes or sections.
  • Rollback plan: how you revert if drift appears.

Define your rules (examples)

Be explicit. Here are common rules that work well:

  • Tags use kebab-case: #project-management not #ProjectManagement
  • A note has at most 5 tags
  • Replace ## Todo with ## Tasks
  • Convert loose checkboxes into a ## Tasks list

Dry run prompt

Start with a plan-only prompt:

  • "Propose how you would normalize tags and headings for notes in this folder. Do not write files yet. List the exact rules you will apply and call out edge cases."

Once the plan looks right:

  • "Now propose file edits for the first 10 notes. Keep approvals on. Do not change meaning, only structure and tags."

Approve diffs, not intentions

When SystemSculpt proposes changes:

  • Read the diff
  • Reject anything that changes meaning
  • Prefer smaller edits over one giant refactor

Failure modes + fixes

  • Failure mode: Cleanup expands from one folder into uncontrolled vault-wide edits. Fix: Lock explicit scope in prompt and approvals before every batch.
  • Failure mode: Rules are too vague, so output style drifts between notes. Fix: Write concrete before/after examples for tags and headings.
  • Failure mode: Semantic meaning is altered during "formatting" changes. Fix: Reject meaning drift and rerun with stricter "structure only" instructions.

Definition of done

I count this cleanup workflow as complete when:

  • Naming and heading rules were applied to the scoped batch without meaning drift.
  • At least one manual spot-check passes after changes are written.
  • The rule set is updated based on the first batch before scaling wider.

Next step based on your intent

If you want a repeatable starting point, use the Obsidian Vault Cleanup Checklist.

Related workflows

Get new workflows by email

Monthly workflow drops, release notes, and tips. No spam.

Try SystemSculpt

SystemSculpt runs workflows inside Obsidian with approvals, semantic search, and streaming chat.