chore: remove the false --body-file rule from the user-level groom-issue skill
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 1/5
- 预计耗时
- 1 小时以内
- 新手友好度
- 1/100
- Issue 类型
- 文档
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 领域
- tooling
调研方向
The issue identifies two passages in the user-level groom-issue skill file, ~/.claude/skills/groom-issue/SKILL.md, and gives their exact wording. Read those passages and remove the inline-body prohibition and its stated reason, while retaining the file-based gh issue edit <N> --body-file <temp-file> step. Done when the acceptance criteria hold and the groomed marker and heading names are unchanged.
由索引模型根据 Issue 内容生成。
描述
Found while auditing the pipeline for #400 (piece 2). This is a fix to a file on the owner's machine, not a change in this repo, so there is no PR.
Problem
The user-level skill ~/.claude/skills/groom-issue/SKILL.md carries the --body-file rule that #400 cut everywhere else. The stated reason ("inline bodies and heredocs mangle backticks, angle brackets, pipe characters, and $") is wrong for Git Bash: a heredoc with a quoted delimiter passes those characters through unchanged. The only real mangle is an argument that starts with /. See the #400 decisions comment (piece 2, "--body-file rule cut everywhere"): https://github.com/nevridge/TaskFlow/issues/400#issuecomment-6697965229. That comment lists groom-issue and pr-triage as the two user-level skills edited by hand. The pr-triage half is scope item 6 of #432.
Two places in the file:
- Line 111: "Delete the temp file afterward. Never pass the body inline via
--body— inline bodies and heredocs mangle backticks, angle brackets, pipe characters, and$." - Line 137, in the rules list: "All
ghbody arguments use--body-file, never--body. Write to a temp file, pass--body-file, then delete the temp file."
Change
- Delete the line 137 bullet.
- In line 111, delete the "Never pass the body inline ... mangle ..." sentence. Keep the step above it (write the assembled body with the Write tool, then
gh issue edit <N> --body-file <temp-file>): a long groomed body is simpler to pass from a file, andpr-triagekeeps--input <file>for the same reason. Say it as a method, not as a rule with a false reason. - If a failure shows up later, put back one line with the real reason.
Acceptance criteria
~/.claude/skills/groom-issue/SKILL.mdno longer says to never pass a body inline, and no longer gives the mangling reason.- The step that writes the body to a file and runs
gh issue edit <N> --body-filestill works as before. - No other change to the skill, in particular the groomed marker on the first line and the heading names.
Out of scope
- The
pr-triageedits (#432), thespec-writerdead tools (#430) and theux-testaudit (#431).
- 主要语言
- C#
- 星标
- 1
- 派生
- 0
- 平均合并
- 2 小时 2 分钟
- 30 天内合并 PR
- 98
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
nevridge/TaskFlow 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 65/100
维护者通常 1 天内回复
-
tech-debt
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
查看 nevridge/TaskFlow 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 74/100
juandresrodca/AdminForge#54 ·
-
要トリアージ 辞書
难度 1/5 1-3 小时 新手友好度 86/100
yksr-melt/Meltype#1625 · 1 个 reaction ·
维护者通常 1 天内回复
-
Docs typo未关闭
难度 1/5 1 小时以内 新手友好度 78/100
MonoGame/docs.monogame.github.io#328 · 1 条评论 ·
-
难度 2/5 1-3 小时 新手友好度 70/100
space-wizards/RobustToolbox#7197 ·
维护者通常 1 天内回复
-
documentation high priority
难度 2/5 1-3 小时 新手友好度 76/100
lachydotmcg/capri-desktop#201 ·
维护者通常 1 天内回复