Save Thread

nowledge-co/community/nowledge-mem-copilot-cli-plugin/skills/save-thread

作者 nowledge-co1f4d7eb61466dbfc93ce8d7a0a806c4d4a196dd0无许可证收录于 2026年10月9日更新于 2026年10月9日

Save a summary of the Copilot CLI session on explicit user request. Copilot lifecycle hooks already capture full transcripts automatically — this skill creates a concise summary thread.

AI 生成的概览

在用户明确要求时,将 Copilot CLI 会话的简要摘要保存为 nmem 线程。

功能
该技能指示智能体根据当前 Copilot CLI 对话撰写简要摘要,并使用 nmem 命令行工具将其保存为线程。内容涵盖何时保存、带标题和来源标记的具体命令格式,以及包含线程 ID 的简短确认回复。它还说明了自动生命周期记录、摘要线程与提炼记忆之间的区别。
适用场景
当用户明确要求保存、设置检查点或记录当前会话时使用。它面向按需摘要保存,而非自动记录完整对话。
运行要求
需要 PATH 中可用的 nmem CLI(nmem-cli)以及可连接的 nmem 服务器;建议通过 pip 或 Arch Linux 包管理器安装。不附带脚本,仅为说明文档。

Save Thread

When to Save

Only when user explicitly says: "Save this session" | "Checkpoint this" | "Record conversation"

Lifecycle hooks capture full session transcripts automatically after responses, before compaction, and at session end. This skill is for on-demand summary saves.

Tool Usage

Create a summary thread via nmem t create:

bash
nmem t create "A concise summary of this session: what was discussed, what was built, and key decisions made" \  --title "Copilot CLI: <short title from first user message>" \  -s copilot-cli

Important: Write the summary yourself from the current conversation context. Do NOT try to invoke the stop hook script directly — it requires hook payload from Copilot CLI internals.

Thread vs Memory

Automatic lifecycle capture stores real session messages. This skill stores a concise summary thread. Memory stores distilled insights. They are different purposes, and a valuable session can use more than one.

Response

text
✓ Thread savedSummary: {summary}Thread ID: {thread_id from nmem output}

Troubleshooting

If nmem is not in PATH: pip install nmem-cli, or on Arch Linux yay -S nmem-cli / paru -S nmem-cli

Run nmem status to check server connection.

来源与署名

来源:nowledge-co/community位于nowledge-mem-copilot-cli-plugin/skills/save-thread提交1f4d7eb

许可证: 无许可证

内容归原作者所有。SourceWeft 从公开仓库中收录这些内容。

举报或申请下架