write-create-or-replacelisted

# write-create-or-replace Call the obsidian-router `write_file` MCP tool with arguments parsed from $ARGUMENTS. ## Arguments **Required**: - `path` — file path relative to vault root. - `content` — full markdown content (frontmatter + body). **Optional**: - `vault` — vault name. Omit for default. - `ifNew` — if true, fail with HTTP 409 when the file already exists. Default false (overwrite). - `ifMatch` — a `contentSha256` from a prior `get_file` of this file. The write is refused with a 409 conflict if the file changed since you read it (optimistic concurrency). Use it whenever another session — or an Obsidian edit — could have touched the file between your read and your write. Atomic when the vault runs the bridge plugin ≥ 0.7.0, otherwise a GET-compare fallback. Mutually exclusive with `ifNew`. ## Argument parsing from $ARGUMENTS - the user usually wants to give the path on the slash line and the content in a follow-up turn → if the slash line gives only a path, ask for the content - `path=X content="..."` for full one-shot - `--if-new` or `ifNew=true` → set `ifNew` - `ifMatch=<hash>` → set `ifMatch` ## Read-modify-write safely (ifMatch) When you are rewriting a file whose current content matters (appending to a running note by full replace, editing a shared scaffold like `hot.md`/`catalog.md`), do it as a conditional write: 1. `get_file` the path → note the `contentSha256` it returns. 2. Build the new full content from what you read. 3. `write_file` with `ifMatch