Repository navigation
refactor(plugins): give the three non-prerequisite check skills distinct names so no check leaf remains #12489
Description
Refs #7582
Blocked by #12488
Outcome
No skill in this repository keeps the leaf name check, which removes the Cursor /check collision the owner observed (D82, Q179). Three check skills are not prerequisite checks (#11956), so the waves do not delete them:
instruction-placement:check: a pass/fail gate over.claude/rules/globs and the rules index;skill-quality:check: skill-authoring QA;toolchain:check: build, test and lint of changed files.
Each one gets a distinct leaf name, and a first description clause that sets it apart from the others. New names are chosen with /naming:name-it-better and swept with /docs-hygiene:rename-references.
Size: the three skill directories hold 118,814 tracked bytes at b000bb5 (instruction-placement 16,565, skill-quality 53,193, toolchain 49,056). A directory rename measured with --no-renames counts as a full delete plus a full add. There are about 323 references to update: /toolchain:check 193, /skill-quality:check 107, /instruction-placement:check 23. So this slice almost certainly exceeds one lane patch.
Done when
- A comment here gives a sized plan: the measured
git diff --no-renamesbyte size of each rename, with references included, and a split into sub-slices, each under 262144 bytes. -
ls -d plugins/*/skills/check 2>/dev/null | wc -lgoes from 3 to 0. -
git grep -c -E '/(instruction-placement|skill-quality|toolchain):check([^a-z0-9-]|$)' -- . ':!**/CHANGELOG.md' ':!.changes/**'prints nothing. - Each renamed skill's description starts with a clause no other installed skill's description starts with.
- Eval evidence of no loss of triggering, per
plugins/playbooks/skills/skill-authoring/reference/skill-criteria.md: a description change re-measures triggering on the probes, and each skill's existing evals run with/evals:plugin-eval --baseline <before.json> --margin <m>and show non-inferiority. -
scripts/validate-plugins.shpasses, and so doesbash scripts/sync-shared-copies.sh --check-bump origin/main. - Host-run (Q179): after merge, a picker label re-observation in Claude Code and in Cursor shows no
/checkcollision, posted here with the client versions. - A merge probe is posted per D82/Q186 for each sub-slice.
Out of scope
- The 32 prerequisite-check skills (waves 1 to 3).
- Changing what any of the three skills does.
Related
- skill-quality: skill authoring, quality and catalog #7582 (parent), chore(skill-quality): recount the *:check skills and size their consolidation #11956 (recount), wave 3 refactor(plugins): delete the 10 external-tool check and check-prerequisites skills (*:check wave 3) #12488 (it touches the same three plugins and
docs/contracts/prerequisites/README.md:156-158).
Activity
github-actions commentedon Nov 2, 2026
Proposed work class: work-class: structural
Basis: automated intake triage; the lanes App applied this class.
Size: Large
Complexity: Medium
Uncertainty: Knowable
Flags: none
Blocked by: #12488
Understood: rename the three non-prerequisite
checkskills (instruction-placement:check,skill-quality:check,toolchain:check) to distinct leaf names, with distinct description openers. Then sweep about 323 references, so that nocheckleaf remains and the Cursor/checkcollision goes away.The issue itself says this exceeds one lane patch. Its first done-when item is a sized plan split into sub-slices under 262144 bytes each, and the work should be split that way.
Wave 3 (#12488) touches the same plugins, so this should follow it. The new names are an implementation choice (
/naming:name-it-better), not an open intent question.The post-merge Cursor and Claude Code picker check needs a host run. It is outside what an unattended lane can do, and it doesn't hold the rest.
No duplicates found among the open issues.
Automated triage, applied by the lanes App.
melodic-automation-lanes commentedon Nov 2, 2026
Not admitted to the issue lane: its done-when asks for what an unattended lane run cannot perform: item 5 (a paid eval: "Eval evidence of no loss of triggering, per plugins/playbooks/skills/skill-au..."); recommended split: keep the other items here as the admissible issue and move these to a child issue for the owner, since a paid eval can bill the owner; it carries host-run; Size large: the split into sub-issues at intake is pending (owner Q93). Admission takes the issue once each of those is met, when intake triages it again (
.github/actions/resolve-config/admission-rules.json).melodic-automation-lanes commentedon Nov 2, 2026
The latest triage verdict holds nothing: admission moved the issue to
status: needs-decision; its comment says why.kyle-sexton commentedon Nov 2, 2026
Status: split into three rename PRs. The issue-triage session splits this issue into three sub-issues, one rename per skill, each its own pull request. The rename has to split because:
--no-renamesrename counts each directory twice: 2 × 118,814 tracked bytes is about 238 KB before any reference edit.git grep -con main)..github/scripts/work-resolve-issue/report-outcome.mjs:456).Estimated sizes per rename:
instruction-placement:checkabout 48 KB,skill-quality:checkabout 175 KB,toolchain:checkabout 210 KB. These are estimates (rename bytes doubled, about 800 bytes per edited reference line). Each sub-issue's pull request states its measuredgit diff --no-renamessize.The renames have no order among them. Each is blocked by #12488, which edits the same three plugins.
Item 5's eval is not an owner item:
claude plugin evalruns model calls on the operator's account (plugins/evals/skills/plugin-eval/SKILL.md:175).docs/contracts/loop-lane/README.md:349).host-run, and its host run uses non-Fable models so no usage credits bill (docs/contracts/loop-lane/README.md:775-776).Each sub-issue carries items 3, 4, 5, 6 and 8 of this issue's body as written, with a Scope line naming its skill.
This issue keeps three items of its body, unchanged:
git diff --no-renamesbyte size. It is met once the three sub-issues' measured sizes are posted here.ls -d plugins/*/skills/check 2>/dev/null | wc -lgoing from 3 to 0. It is met after the last sub-issue merges.kyle-sexton commentedon Nov 3, 2026
Decision recorded. Owner answer, quoted verbatim, given in the lane 2 session on 2026-11-03 when asked to pick a new leaf name for
instruction-placement:check(#12497):This issue's only stated reason for the renames is the Cursor
/checkcollision (Outcome: "which removes the Cursor/checkcollision the owner observed (D82, Q179)"). Soinstruction-placement:check,skill-quality:checkandtoolchain:checkkeep thecheckleaf, and this issue and its three rename slices close as not planned: #12497, #12498, #12499. Nothing was renamed, and no branch or PR exists for any of them.Posted by the lane 2 session.