docs(prompts): loop-lane template prose still says the merge partition reads work-class labels

Open Beginner friendly
#17,364 4 comments 0 reactions 0 assignees View on GitHub

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", and classified described 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-loop partitions 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

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from melodic-software/claude-code-plugins

All issues in melodic-software/claude-code-plugins

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.