fix(work-items): decompose publish snippet is refused in worktree-isolated sessions
I maintainer di solito rispondono entro 1 giorno
Una pull request collegata è già stata integrata.
- #7090 di @kyle-sexton — integrata
Valutazione
- Difficoltà
- 3/5
- Tempo stimato
- 1-2 giorni
- Idoneità per principianti
- 35/100
Direzione di ricerca
Start with the step 4 publish snippet in plugins/work-items/skills/decompose/SKILL.md, which combines a git rev-parse command substitution with a $(cat "$BODY_FILE") body argument, then read the create-item path in work-item-tracker.sh. Reproducing the refusal needs a worktree-isolated Claude Code session, and whether a --body-file option already exists is unconfirmed. Done means the documented publish runs from a worktree-isolated session without a wrapper, and the same check covers /work-items:track add.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Summary
/work-items:decompose step 4's publish snippet is refused in a worktree-isolated session, so a decompose run from a worktree cannot publish slices as written.
What happened
Publishing the approved breakdown for #6917 from a worktree-isolated session, every create-item call shaped like the step 4 snippet was refused by Claude Code's worktree isolation:
this command names git in a form too complex to verify that it stays inside the worktree. Refusing to run it
Both tracker paths (main checkout and worktree copy) were refused when the body was passed inline as --body "$(cat "$BODY_FILE")". The run only published after the agent moved the call into a wrapper script that runs the worktree's copy of work-item-tracker.sh. Nothing was created by the refused attempts.
Likely cause (inference, not yet reproduced in isolation)
The snippet in plugins/work-items/skills/decompose/SKILL.md step 4 combines:
- a fallback
TRACKER="${CLAUDE_PROJECT_DIR:-$(git rev-parse --show-toplevel)}/...", which putsgitinside a command substitution; and --body "$(cat "$BODY_FILE")", another command substitution in the same invocation.
Claude Code documents that in an isolated worktree it "blocks a Bash or Monitor command when it can't verify from the command text that any git the command runs stays inside the worktree" (worktrees: how Claude Code enforces isolation). The tracker script itself runs gh/git, which the command-shape check cannot see through.
Fix direction
Give create-item a --body-file input (or document one if it exists) and split the snippet into plain commands with literal paths, so no git or command substitution appears in the publishing command. Same check for other skills that reuse this snippet (/work-items:track add).
Verification
- A decompose publish from a worktree-isolated session succeeds with the documented snippet, no wrapper.
- Related precedent: #5696, #6234 (other worktree-isolation refusals of our commands).
No related issue: found during the #6917 publish; not covered by #5696 or #6234.
- Lingua principale
- Shell
- Stelle
- 22
- Fork
- 2
- Merge medio
- 8h 27m
- PR unite (30g)
- 957
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di melodic-software/claude-code-plugins
-
priority: medium
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
melodic-software/claude-code-plugins#7351 · 2 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
agent-ready priority: high work-class: scoped
Difficoltà 2/5 1-3 ore Idoneità per principianti 74/100
melodic-software/claude-code-plugins#7312 · 3 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
priority: medium
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
melodic-software/claude-code-plugins#7288 · 2 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
knowledge: docpage-digest dual verification defines no verdict vocabulary or pass/fail thresholdApertaneeds-human
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
melodic-software/claude-code-plugins#7286 · 2 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
priority: low
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
melodic-software/claude-code-plugins#7282 · 2 commenti ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di melodic-software/claude-code-plugins
Issue simili
-
area:contributor-experience difficulty:easy good first issue Stellar Wave
Difficoltà 2/5 1-3 ore Idoneità per principianti 62/100
I maintainer di solito rispondono entro 2 giorni
-
package-update
Difficoltà 2/5 1-3 ore Idoneità per principianti 62/100
oSoWoSo/vOid_Community_repOsitory#436 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
documentation good first issue
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
Maki-Zeninn/stellar-router#1485 ·
I maintainer di solito rispondono entro 1 giorno
-
Pin pnpm 9 with a packageManager fieldForse già presa @Rohit-Solanki1890 l’ha presa oggi. Apertadevops dx good first issue
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 82/100
StellarLock/StellarLock#980 · 2 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
hestiacp/hestiacp#5798 · 2 commenti ·
I maintainer di solito rispondono entro 1 giorno