feat(work-items): route an undiagnosed bug through diagnosis on the autonomous path
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 38/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- shell
调研方向
Start from plugins/work-items/skills/work/ and the triage skill that already documents unknown-root-cause routing after #6279 / PR #6296. Decide a marker (brief text or an existing status label; new labels need the GitHub infrastructure repo) that unattended triage writes when a bug is autonomous-eligible but undiagnosed. Teach /work-items:work to run diagnosis first when that marker is present, then continue to implement; named root causes must still skip diagnosis. Done when the three acceptance bullets hold for unattended triage.
由索引模型根据 Issue 内容生成。
描述
Problem
#6279 (PR #6296) taught /work-items:triage that a verified bug is not a diagnosed one: an unknown root cause routes to /debugging:debug (or /testing:diagnose) before any fix.
That routing is prose only. When triage runs unattended and marks a bug autonomous-eligible, /work-items:work never reads it, so the item still goes triage → work → implement and skips diagnosis. plugins/work-items/skills/work/ has no diagnosis route. Codex raised this as a P1 on PR #6296, thread PRRT_kwDOTCGFQM6o0otp.
Proposed fix
- Triage records the "root cause unknown" state on the item in a form
/work-items:workcan act on: a marker in the brief, or an existing status label. New labels go through the GitHub infrastructure repository. /work-items:workruns the diagnosis step first when the marker is present, then continues to the fix.
Acceptance
- An unattended triage of a bug whose root cause is unknown leaves a marker
/work-items:workreads. -
/work-items:workroutes that item through diagnosis before implement. - A bug whose root cause is already named still goes straight to the fix.
- 主要语言
- Shell
- 星标
- 22
- 派生
- 2
- 平均合并
- 5 小时 11 分钟
- 30 天内合并 PR
- 838
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
melodic-software/claude-code-plugins 的其他 Issue
-
good first issue needs-triage priority: medium
难度 2/5 1-3 小时 新手友好度 72/100
melodic-software/claude-code-plugins#6631 · 1 条评论 ·
维护者通常 1 天内回复
-
needs-triage
难度 2/5 1-3 小时 新手友好度 78/100
melodic-software/claude-code-plugins#6547 ·
维护者通常 1 天内回复
-
needs-triage
难度 2/5 1-3 小时 新手友好度 76/100
melodic-software/claude-code-plugins#6535 ·
维护者通常 1 天内回复
-
test_comment_census.py: SccArgv flag-shaped-filename test errors on Windows (#!/bin/sh scc shim)未关闭good first issue needs-triage priority: low
难度 2/5 1-3 小时 新手友好度 72/100
melodic-software/claude-code-plugins#6532 · 1 条评论 ·
维护者通常 1 天内回复
-
good first issue needs-triage priority: low
难度 2/5 1-3 小时 新手友好度 72/100
melodic-software/claude-code-plugins#6390 · 1 条评论 ·
维护者通常 1 天内回复
查看 melodic-software/claude-code-plugins 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 78/100
-
难度 2/5 1-3 小时 新手友好度 72/100
gnosis/gnosis_vpn#540 ·
维护者通常 1 天内回复
-
bug milestone-qa
难度 2/5 1-3 小时 新手友好度 74/100
lognorman20/monaco#3901 ·
-
Lid close does not lock the session on Apple Silicon (lid-close bind skips omarchy-system-lid-close)未关闭
难度 1/5 1-3 小时 新手友好度 90/100
omacom/omarchy-mac#701 · 1 条评论 ·
维护者通常 1 天内回复
-
A 20.x release after 21.0.0 would move `latest` back to 20.x, and `next` stays on the release candidate可能已有人在做 @armando-navarro 今天认领。 未关闭comp: build/pipeline type: bug version: current (v17+)
难度 2/5 1-3 小时 新手友好度 85/100
angular/angularfire#3790 ·
维护者通常 3 天内回复