write-bundlelisted

Run several vault writes as ONE logical operation with rollback — the note + the index + the journal + hot.md either all land, or none do. Use whenever a single user-visible action touches 2+ files and a half-written result would be wrong. Also the recovery entry point for bundles a crash left unfinished. EN triggers: "write these files together", "all or nothing", "make this atomic", "roll back if any of it fails", "recover the unfinished bundle", "something crashed mid-save". FR triggers : "écris ces fichiers ensemble", "tout ou rien", "rends ça atomique", "annule tout si une étape échoue", "récupère le lot inachevé", "ça a planté au milieu de la sauvegarde". Example / Exemple: EN: "save the note, add it to the index and log it — all three or none" FR: "écris la note, ajoute-la à l'index et journalise — les trois ou aucun"
tboome33/obsidian-mcp-router · ★ 1 · AI & Automation · score 74

Install: claude install-skill tboome33/obsidian-mcp-router

# write-bundle Call the obsidian-router `write_bundle` MCP tool. It runs a list of writes as one journaled operation: every target's content is captured **before** the first write, and if any step fails, every file the bundle touched is put back byte-for-byte. ## When to use Whenever one user-visible action produces **several** files whose half-written state would be wrong: - `save` — the note + the journal line + `hot.md` - `wiki-ingest` — the source page + entity pages + the journal - `wiki-fold` — the fold page + the log rewrite - any multi-key frontmatter update that must not land halfway (this is what makes `merge_frontmatter` all-or-nothing — see below) For a single file, use the ordinary `write-append` / `write-create-or-replace` / `write-patch`. A bundle around one write buys nothing but a journal round-trip. ## Arguments **Required**: `steps` — an ordered array, at most 25. Each entry is `{ op, path, ...that op's own arguments }`. | `op` | runs | needs | |---|---|---| | `write` | `write_file` | `content` | | `append` | `append_to_file` | `content` | | `patch` | `patch_file` | `operation`, `targetType`, `target`, `content` | | `set_frontmatter` | `set_frontmatter` | `key`, `value` | | `merge_frontmatter` | `merge_frontmatter` | `values` | | `delete` | `delete_file` | `confirm: true` | **Optional**: `vault` (omit for default — a bundle is single-vault, steps may not override it) · `preview: true` (sealed plan, writes nothing) · `approvedPlanSha256` (the seal f