fix(implementation): parallel workers collide on shared scratchpad script names
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- shell
- Domain
- developer-experience
Research direction
Find the implementation:implement-dispatch brief template and the implementer agent bodies; the issue does not name their file paths, so search the repository for those terms. Read how the current scratch-file instructions are phrased, then update the brief and agent bodies to require branch-purpose names and prohibit running scripts not written for the task. Done when both locations state the rule; a per-worker subdirectory is optional.
Written by the indexing model from the issue text.
Description
Observed 2026-10-07: workers dispatched in parallel share one session scratchpad. Three times a worker ran another worker's leftover bump.py from that scratchpad, because the names matched, and edited the wrong plugins' versions. One of those runs left uncommitted edits in another worktree. In each case the worker or the user had to revert by hand.
Proposal: the implementation:implement-dispatch brief and the implementer agents should require scratch files to be named <branch>-<purpose>, and should forbid running a scratch script the worker did not write in this task. Also consider a per-worker scratch subdirectory.
Acceptance: the brief template and the agent bodies state the rule. One line is enough; this is an observed stumble under the instruction-economy rule.
- Dominant language
- Shell
- Stars
- 22
- Forks
- 2
- Avg merge
- 5h 11m
- Merged PRs (30d)
- 838
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from melodic-software/claude-code-plugins
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
melodic-software/claude-code-plugins#6547 ·
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
melodic-software/claude-code-plugins#6535 ·
Maintainers usually reply within 1 day
-
test_comment_census.py: SccArgv flag-shaped-filename test errors on Windows (#!/bin/sh scc shim)Opengood first issue needs-triage priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
melodic-software/claude-code-plugins#6532 · 1 comment ·
Maintainers usually reply within 1 day
-
good first issue needs-triage priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
melodic-software/claude-code-plugins#6390 · 1 comment ·
Maintainers usually reply within 1 day
-
good first issue needs-triage priority: low
Difficulty 1/5 Under an hour Newbie friendliness 88/100
melodic-software/claude-code-plugins#6386 · 1 comment ·
Maintainers usually reply within 1 day
All issues in melodic-software/claude-code-plugins
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
gnosis/gnosis_vpn#540 ·
Maintainers usually reply within 1 day
-
Lid close does not lock the session on Apple Silicon (lid-close bind skips omarchy-system-lid-close)Open
Difficulty 1/5 1-3 hours Newbie friendliness 90/100
omacom/omarchy-mac#701 · 1 comment ·
Maintainers usually reply within 1 day
-
A 20.x release after 21.0.0 would move `latest` back to 20.x, and `next` stays on the release candidatePossibly taken @armando-navarro claimed this today. Opencomp: build/pipeline type: bug version: current (v17+)
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
angular/angularfire#3790 ·
Maintainers usually reply within 3 days
-
ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
LucasSantana-Dev/Lucky#2698 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
collabnix/awesome-mcp-lists#179 ·
Maintainers usually reply within 1 day