docs(prompts): loop-lane template prose still says the merge partition reads work-class labels
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 71/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- markdown
- Domain
- documentation
Research direction
Read the merged #12866 change and the "no work-class label is read" passage in plugins/source-control/skills/babysit-loop/SKILL.md to learn how the rung-based merge partition works, then open prompts/loops/loop-lane-prompts.md at the four cited spots (Per-repository profile, Adopting a new repository steps 2-4, and the Section 3 and 3b copy blocks). Rewrite each to describe the rung partition rather than work-class: labels, or delete passages that only sized a label migration. Done when no passage still claims the merge partition reads work-class labels.
Written by the indexing model from the issue text.
Description
Problem
#12866 moved the babysit merge partition from work class to rung: no rung reads a work-class: label, and the provenance: untrusted hold is the one class hold (plugins/source-control/skills/babysit-loop/SKILL.md, "no work-class label is read"). prompts/loops/loop-lane-prompts.md still says otherwise outside the copy blocks the dedupe PR aligned:
- "Per-repository profile", the classification-count bullet: "The merge partition reads the recorded class from the
work-class:label only", andclassifieddescribed as "the merge-eligible population the rung decision reads". - "Adopting a new repository", steps 2 to 4: "a repo with no label axis is entirely human-merge", "the label axis is what makes a rung reachable", "an item whose class is recorded only as a body trailer is ineligible at every rung".
- Section 3 (Attended queue) copy block: "the label because
babysit-looppartitions on it". - Section 3b copy block: "If no label axis exists ... Nothing auto-merges there, which is the baseline".
Done when
Each passage states the rung-based partition, or is removed where it only existed to size a label migration for the merge rung.
- Dominant language
- Shell
- Stars
- 22
- Forks
- 2
- Avg merge
- 1h 47m
- Merged PRs (30d)
- 942
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
-
Own-agent checks: reject the Actions bot id in admit.mjs and test the source label in pr-verifyOpen
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
melodic-software/claude-code-plugins#17374 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
melodic-software/claude-code-plugins#17039 · 7 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
melodic-software/claude-code-plugins#16931 · 3 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
melodic-software/claude-code-plugins#15498 · 3 comments ·
Maintainers usually reply within 1 day
-
session-flow: remove a delivered absence's away state so idle hook cost returns to the cheap pathPossibly taken @kyle-sexton claimed this today. Open
Difficulty 3/5 1-2 days Newbie friendliness 18/100
melodic-software/claude-code-plugins#17389 · 4 comments ·
Maintainers usually reply within 1 day
All issues in melodic-software/claude-code-plugins
Similar issues
-
application-issue
Difficulty 1/5 Under an hour Newbie friendliness 82/100
Installomator/Installomator#3657 · 1 comment ·
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
nekko-labs/nekko-agent#2998 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 60/100
kenzok8/openwrt-honk#35 ·
Maintainers usually reply within 1 day
-
bug severity:medium triage:confirmed triage:in-progress
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Cotal-AI/Cotal#7795 · 1 comment ·
Maintainers usually reply within 1 day