Back to Details

session-handoff

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Session Handoff

会话交接

Different from wrap-up. Wrap-up is a checklist for you. Handoff is a document written for the next session.
这与会话收尾不同。会话收尾是供你使用的检查清单，而交接文档是写给下一次会话的。

Trigger

触发场景

Use when saying "handoff", "continue later", "pass to next session", "session transfer", or ending a session and wanting to resume smoothly.
当你说“交接”“稍后继续”“传递给下一次会话”“会话转移”，或结束会话并希望顺利恢复工作时使用。

Workflow

工作流

  1. Gather current state from git.
  2. List completed, in-progress, and pending work.
  3. Note key decisions made and their reasoning.
  4. Capture any learnings from this session.
  5. Generate a resume command for the next session.
  1. 从 git 收集当前状态。
  2. 列出已完成、正在进行和待处理的工作。
  3. 记录已做出的关键决策及其原因。
  4. 记录本次会话中的经验教训。
  5. 为下一次会话生成恢复命令。

Commands

命令

bash
git status
git diff --stat
git log --oneline -5
git branch --show-current
bash
git status
git diff --stat
git log --oneline -5
git branch --show-current

Output

输出

markdown
undefined
markdown
undefined

Session Handoff — [date] [time]

会话交接 — [日期] [时间]

Status

状态

  • Branch: feature/xyz
  • Commits this session: 3
  • Uncommitted changes: 2 files modified
  • Tests: passing / failing / not run
  • 分支：feature/xyz
  • 本次会话的提交数：3
  • 未提交的更改：修改了 2 个文件
  • 测试：通过 / 失败 / 未运行

What's Done

已完成

  • [completed task 1]
  • [completed task 2]
  • [已完成任务 1]
  • [已完成任务 2]

What's In Progress

正在进行

  • [current task with context on where you stopped]
  • [file:line that needs attention next]
  • [当前任务，并附上停止位置的上下文]
  • [接下来需要处理的文件:行号]

What's Pending

待处理

  • [next task that hasn't been started]
  • [blocked items with reason]
  • [尚未开始的下一步任务]
  • [受阻事项及原因]

Key Decisions Made

已做出的关键决策

  • [decision 1 and why]
  • [decision 2 and why]
  • [决策 1 及其原因]
  • [决策 2 及其原因]

Learnings Captured

已记录的经验

  • [Category] Rule (from this session)
  • [类别] 规则（来自本次会话）

Files Touched

涉及的文件

  • path/to/file1.ts
    — [what changed]
  • path/to/file2.ts
    — [what changed]
  • path/to/file1.ts
    — [改动内容]
  • path/to/file2.ts
    — [改动内容]

Gotchas for Next Session

下一次会话的注意事项

  • [thing that tripped you up]
  • [non-obvious behavior discovered]
  • [容易出错的地方]
  • [发现的不明显行为]

Resume Command

恢复命令

Continue working on [branch]. [1-2 sentence context]. Next step: [specific action].
undefined
在 [分支] 上继续工作。[1-2 句上下文]。下一步：[具体操作]。
undefined

Guardrails

注意事项

  • Write for the reader (next session), not the writer.
  • Include specific file paths and line numbers where relevant.
  • The resume command should be copy-pasteable into the next session.
  • Keep it factual — describe changes functionally, don't infer motivation.
  • 面向读者（下一次会话），而不是编写者。
  • 在相关位置包含具体文件路径和行号。
  • 恢复命令应可直接复制粘贴到下一次会话中。
  • 保持客观——从功能角度描述改动，不要推测动机。