| name | siyuan-sisyphus-create-edit |
| description | CLI-only playbook for creating and editing SiYuan documents and blocks with siyuan-sisyphus. Use for path-based document creation, block append/insert/update, metadata, daily notes, and verified edits. |
Create and Edit SiYuan Content with the CLI
Read the target first, choose the highest-level action that preserves intent, perform one bounded change, then read it again.
Create documents
Use a workspace path for convenient path-based creation:
siyuan-sisyphus fs write --path '/Notebook/Project/Notes' --markdown '# Notes
Initial content.' --json
Use a notebook ID plus notebook-local hpath when low-level control is needed:
siyuan-sisyphus document create --notebook '<notebook-id>' --path '/Project/Notes' --markdown '# Notes' --json
Do not include the notebook name in the low-level hpath.
Edit blocks
siyuan-sisyphus block append --parent-id '<doc-id>' --data-type 'markdown' --data '## New section
Paragraph.' --json
siyuan-sisyphus block insert --previous-id '<block-id>' --data-type 'markdown' --data 'Inserted paragraph.' --json
siyuan-sisyphus block update --id '<block-id>' --data-type 'markdown' --data 'Replacement block content.' --json
Use block update only when replacing the whole block is intended. Prefer a scoped replacement for a small textual change:
siyuan-sisyphus block replace --id '<block-id>' --edit-json '{"old":"draft","new":"final"}' --json
Metadata and daily notes
siyuan-sisyphus block set-attrs --id '<block-id>' --attrs-json '{"custom-source":"agent"}' --json
siyuan-sisyphus document create-daily-note --notebook '<notebook-id>' --json
Before rename, move, delete, or broad replacement, resolve the exact target, show the affected scope, and obtain approval. After every mutation, read by stable ID when possible. Use siyuan-sisyphus help block append when any parameter is uncertain.
