pr-pipeline: address-feedback composite activity and its leaves
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 15/100
- Issue 类型
- 功能
- 描述清晰度
- 需要澄清
- 活跃度
- 活跃
- 领域
- ci-cd
调研方向
This is a tracking issue for the address-feedback composite and its three draft leaves (fix-finding, reply-to-thread, resolve-thread) in the pr-unblock lane, which is parent issue #6989. Start by reading how the pipeline config defines composite and leaf activities for resolve-conflicts and fix-ci, since the payload does not name specific files. Open questions are per-source leaf design and thread-resolution rules, so this needs a maintainer decision before code. Done means each leaf is defined in the config with its effect, enabled per repository, and its first live run recorded.
由索引模型根据 Issue 内容生成。
描述
Refs: #6989
The pr-unblock lane (stage unblock) composes three activities: resolve-conflicts, fix-ci and
address-feedback. Activities are layered: a composite activity lists child activities, and only
leaves run a skill or script with their own effect. This issue tracks the address-feedback
composite and its leaves so none is lost while pr-unblock ships with resolve-conflicts only.
Leaves (draft)
-
fix-finding: push a fix for a review finding (branch write) -
reply-to-thread: answer a thread that needs no code change (pull-request write) -
resolve-thread: resolve a thread after a pushed commit addresses it (pull-request write)
Per review source (Codex, Claude, human), decide whether each source needs its own leaf or an input
to the leaves above. Threads opened by humans are never resolved by a lane.
Done when
Each leaf is defined in the pipeline config with its effect, enabled per repository, and its
first live run is recorded.
🤖 Generated with Claude Code
- 主要语言
- Shell
- 星标
- 22
- 派生
- 2
- 平均合并
- 8 小时 25 分钟
- 30 天内合并 PR
- 944
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
melodic-software/claude-code-plugins 的其他 Issue
-
good first issue priority: low
难度 2/5 1-3 小时 新手友好度 62/100
melodic-software/claude-code-plugins#7530 · 1 条评论 ·
维护者通常 1 天内回复
-
needs-human priority: medium
难度 2/5 1-3 小时 新手友好度 65/100
melodic-software/claude-code-plugins#7455 · 1 条评论 ·
维护者通常 1 天内回复
-
priority: medium
难度 2/5 1-3 小时 新手友好度 68/100
melodic-software/claude-code-plugins#7351 · 2 条评论 ·
维护者通常 1 天内回复
-
agent-ready priority: high work-class: scoped
难度 2/5 1-3 小时 新手友好度 74/100
melodic-software/claude-code-plugins#7312 · 3 条评论 ·
维护者通常 1 天内回复
-
priority: medium
难度 2/5 1-3 小时 新手友好度 76/100
melodic-software/claude-code-plugins#7288 · 2 条评论 ·
维护者通常 1 天内回复
查看 melodic-software/claude-code-plugins 的全部 Issue
相似的 Issue
-
area: compat area: parsing bug
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
Micke-K/IntuneManagement#441 ·
-
review-2026-10 Trad En
难度 2/5 半天 新手友好度 70/100
zigbeefordomoticz/wiki#302 ·
-
Add dependabot未关闭feat
难度 2/5 1 小时以内 新手友好度 72/100
open-nudge/opentemplate#204 ·
维护者通常 1 天内回复
-
omarchy-brightness-keyboard: double idle-blank saves brightness 0, so wake 'restore' keeps the keyboard backlight off可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复