一键在 Manus 中运行任何 Skill

oh-my-obsidian-session-save

星标27

分支0

更新时间2026年4月24日 00:49

Use this skill when the user explicitly wants to save, record, or summarize the current session into the Obsidian vault.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

hongdangmoo49

hongdangmoo49/oh-my-obsidian

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Oh My Obsidian Session Save

Use this skill when the user explicitly wants to save, record, or summarize the current session into the Obsidian vault.

Contract

Mutating use requires a resolved vault with setup-state.status == "complete".
Never overwrite an existing note. Use exclusive create or a collision suffix.
Save under 작업기록/<category>/YYYY-MM-DD_<slug>.md.
Inspect git status first.
If unrelated staged, unstaged, or ambiguous git state exists, create the note but skip staging and commit, then report that clearly.
If git is safe, stage only the created note, commit it, and verify the index is clear for that path after commit.
If the resolver fails or setup is incomplete, surface the helper guidance and direct the user back to the oh-my-obsidian setup skill.

Helper

node scripts/vault-ops.mjs session-save \
  --topic "<topic>" \
  --detail "<summary>" \
  --category "세션기록"

Optional repeated flags:

--decision "<item>"
--next-step "<item>"
--file "<path>"
--participant "<name>"
--tag "<tag>"
--type "<type>" — auto-derived from category if omitted (session-log|decision|troubleshooting|meeting-notes)
--service "<service>" — repeated, names of affected services
--related-doc "<path>" — repeated, vault-relative path to auto-discover as wikilink

Expected Flow

Derive a concise topic and summary from the session.
Choose the category:
- 세션기록
- 의사결정
- 트러블슈팅
- 회의록
Run the helper. If related documents are discovered in the vault, pass them as --related-doc flags.
Tell the user where the note was written and whether git commit was skipped or completed.
If the helper returns setup guidance instead of writing, stop and route the user to the setup skill instead of improvising a fallback mutation.

同仓库更多 Skills

同仓库

oh-my-obsidian-setup

hongdangmoo49/oh-my-obsidian

Use this skill when the user wants to initialize oh-my-obsidian, create or attach an Obsidian vault, configure persistent vault resolution, or prepare Obsidian Git integration.

2026-04-2727

oh-my-obsidian-restore-history

hongdangmoo49/oh-my-obsidian

Use this skill when the user wants to restore, migrate, or import past Codex session history into the Obsidian vault as structured documents.

2026-04-2427

oh-my-obsidian-recall

hongdangmoo49/oh-my-obsidian

Use this skill when the user asks about previous decisions, earlier fixes, past session notes, troubleshooting history, or knowledge that should already exist in the Obsidian vault.

2026-04-2427

recall

hongdangmoo49/oh-my-obsidian

Automatically recall relevant past context from the Obsidian vault when the user asks about past decisions, previous work, how something was done before, troubleshooting history, or project knowledge. This skill searches the team's knowledge base to provide historical context. Triggers: 회상, 기억나, 이전에, 어떻게 했지, recall, remember, how did we, what did we decide, past decision, 이슈 해결, 작업 기록, 이전 작업, 과거, 히스토리, 히스토리 확인, 찾아줘, 검색, find, search vault, what was the decision on, how was X implemented

2026-04-2427

session-save

hongdangmoo49/oh-my-obsidian

Save current session context and work summary to the Obsidian vault when the user asks to record or save their work. Automatically generates a structured markdown document capturing what was discussed, decisions made, and next steps. Triggers: 기록해, 저장해, save session, 세션 저장, 작업 기록, 이 작업 기록, save this, record this, 기록, 저장, 로그, log, document this, 회의록 작성, 정리해줘

2026-04-2427

oh-my-obsidian-vault-manager

hongdangmoo49/oh-my-obsidian

Use this skill when the user wants to inspect the vault structure, add a new document, organize loose markdown files, or run a vault health check.

2026-04-2327

name	oh-my-obsidian-session-save
description	Use this skill when the user explicitly wants to save, record, or summarize the current session into the Obsidian vault.

Oh My Obsidian Session Save

Use this skill when the user explicitly wants to save, record, or summarize the current session into the Obsidian vault.

Contract

Mutating use requires a resolved vault with setup-state.status == "complete".
Never overwrite an existing note. Use exclusive create or a collision suffix.
Save under 작업기록/<category>/YYYY-MM-DD_<slug>.md.
Inspect git status first.
If unrelated staged, unstaged, or ambiguous git state exists, create the note but skip staging and commit, then report that clearly.
If git is safe, stage only the created note, commit it, and verify the index is clear for that path after commit.
If the resolver fails or setup is incomplete, surface the helper guidance and direct the user back to the oh-my-obsidian setup skill.

Helper

node scripts/vault-ops.mjs session-save \
  --topic "<topic>" \
  --detail "<summary>" \
  --category "세션기록"

Optional repeated flags:

--decision "<item>"
--next-step "<item>"
--file "<path>"
--participant "<name>"
--tag "<tag>"
--type "<type>" — auto-derived from category if omitted (session-log|decision|troubleshooting|meeting-notes)
--service "<service>" — repeated, names of affected services
--related-doc "<path>" — repeated, vault-relative path to auto-discover as wikilink

Expected Flow

Derive a concise topic and summary from the session.
Choose the category:
- 세션기록
- 의사결정
- 트러블슈팅
- 회의록
Run the helper. If related documents are discovered in the vault, pass them as --related-doc flags.
Tell the user where the note was written and whether git commit was skipped or completed.
If the helper returns setup guidance instead of writing, stop and route the user to the setup skill instead of improvising a fallback mutation.