Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

fix(session-flow): settle in-flight work the handoff depends on before writing it

已关闭
  • 哪里不对？
#6,439 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

@kyle-sexton 已经在做这个了。

开始于 2026年10月11日。

  • #7073 来自 @kyle-sexton —— 未关闭

评估

难度
4/5
预计耗时
3-5 天
新手友好度
38/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
markdown, shell
领域
developer-experience, tooling

调研方向

Read plugins/session-flow/skills/handoff/SKILL.md (the Named subagents inventoried this turn checklist) and plugins/session-flow/reference/off-thread-work.md. The skill currently inventories running subagents and still writes the save-point; change that path so work the handoff depends on is waited on, folded in, or explicitly left in flight after the user chooses. Done when a handoff is written only after everything it describes is settled, without free-hand edits to the handoff file.

由索引模型根据 Issue 内容生成。

描述

needs-triage priority: medium

Problem

/session-flow:handoff writes the save-point while subagents the session spawned are still running. When one of them returns after the save, its result lands in the old session, and the handoff file is already stale: its brief, environment, remaining actions and Next: headlines describe the work as still in flight. The user then has to ask for the handoff to be updated, and the update is a hand repair (Edit plus save_point.py validate) of a file the skill says must never be written free-hand.

Observed 2026-10-05: a session wrote a handoff while a naming-tournament subagent was running. The tournament finished seconds later, the user picked a name in the same session, and the handoff had to be patched in five places (brief, completion criteria, environment, open questions, Next:).

Proposed fix

Before new, the skill settles in-flight work instead of only inventorying it:

  • For every subagent this session spawned that is still running, decide whether the handoff's content depends on its result (its output changes the brief, the next action, a decision or a criterion).
  • Dependent and expected to finish: wait for it (the harness re-invokes the session on completion), fold its result in, then write the save-point.
  • Independent of the handoff's content (for example a background dynamic workflow that writes its own durable output and that the next session only reads): hand off without waiting and record it in Environment to re-establish, as today.
  • Stuck or long-running dependent work: say so and let the user choose between waiting, cancelling, or handing off with it recorded as in flight.

The rule in one line: hand off only once everything the handoff describes is settled.

Out of scope

The continuation router's choice between handoff, compaction and clear; prompt-only handoffs with no in-flight work.

Related

  • plugins/session-flow/skills/handoff/SKILL.md "Named subagents inventoried this turn" checklist item (inventories, does not wait)
  • plugins/session-flow/reference/off-thread-work.md

🤖 Generated with Claude Code

主要语言
Shell
星标
22
派生
2
平均合并
3 小时 42 分钟
30 天内合并 PR
938

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

melodic-software/claude-code-plugins 的其他 Issue

查看 melodic-software/claude-code-plugins 的全部 Issue

相似的 Issue

更多 Shell/Bash Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。