obsidian-writer

name	obsidian-writer
description	Save project context and articles to the configured Obsidian Vault, and publish Markdown to docs.jiun.dev through the Vault sync workflow. Use for "obsidian 업로드", "옵시디언 저장", "vault 업로드", "아티클 저장", "문서 공개", "docs 업로드", "외부 공유", or "publish" requests. Use direct server maintenance only when the user explicitly asks to inspect, temporarily push, or delete a docs.jiun.dev document.

Obsidian Writer

Use the bundled writer as the primary path for both private Vault documents and durable public documents.

Load configuration

Read ~/.agents/OBSIDIAN.md through static-index when available. The file must define a valid Vault path. Verify configuration without changing it:

python3 scripts/obsidian-write.py --check-config

Do not publish secrets, credentials, internal addresses, or private operational data. Inspect the final Markdown before making it public.

Choose one mode

Project context

Save project-specific material under workspace/{project}/context/, workspace-vibe/{project}/context/, or workspace-ext/{project}/context/ based on the current working directory:

python3 scripts/obsidian-write.py \
  --title "API 설계" \
  --content "마크다운 내용"

Optional arguments:

• --project NAME: override the detected project
• --subfolder NAME: create a folder below the project context directory
• --filename NAME: choose the filename; a date prefix is added when absent
• --tags a,b: append tags
• --overwrite: replace an exact existing path; otherwise a numeric suffix is added

Private article

Save research or a report under articles/YYYY-MM-DD-slug.md without publishing it:

python3 scripts/obsidian-write.py \
  --article \
  --title "Research title" \
  --content "마크다운 내용" \
  --tags "research,topic"

Durable docs.jiun.dev publication

Use --publish. It implies --article, writes publish: true in frontmatter, and lets vault-docs-sync upload the document within about ten minutes:

python3 scripts/obsidian-write.py \
  --publish \
  --title "Public document" \
  --content "마크다운 내용" \
  --tags "public,documentation"

Expected URL:

https://docs.jiun.dev/#/YYYY-MM-DD-slug

Use standard Markdown links instead of Obsidian wikilinks because Docsify does not render [[wikilinks]] reliably.

Direct server maintenance

Use scripts/docs-publish.sh only for explicit server inspection, temporary sharing, or cleanup. It requires DOCS_HOST and DOCS_URL; DOCS_USER and DOCS_ROOT are optional.

bash scripts/docs-publish.sh list
bash scripts/docs-publish.sh read DOCUMENT_NAME
bash scripts/docs-publish.sh url DOCUMENT_NAME

Direct push and write uploads can be deleted by the next Vault sync when no matching publish: true article exists. Prefer --publish for durable documents.

Before delete, resolve the exact remote document name and confirm the destructive intent unless the user already named that exact document for deletion:

bash scripts/docs-publish.sh delete DOCUMENT_NAME

Sync contract

• publish: true in articles/ means upload and retain.
• Removing publish: true or removing the article causes the sync process to remove the stale server copy.
• LaunchAgent: ~/Library/LaunchAgents/com.jiun.vault-docs-sync.plist
• Sync implementation: ~/workspace/settings/vault-scripts/vault-docs-sync.py
• Logs: /tmp/vault-docs-sync.log and /tmp/vault-docs-sync.err

Resources

• scripts/obsidian-write.py: deterministic Vault writer with project, article, and publish modes
• scripts/docs-publish.sh: direct Docsify server inspection and maintenance
• ~/.agents/OBSIDIAN.md: user-specific Vault configuration