You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
refactor(skill-quality): give skill-quality:check a distinct leaf name #12498
skill-quality:check, the skill-authoring QA gate, gets a distinct leaf name and a first description clause that sets it apart. The new name is chosen with /naming:name-it-better and swept with /docs-hygiene:rename-references. What the skill does is unchanged. This is one of three renames split from #12489. Estimated size: 106,386 bytes of rename (53,193 tracked bytes, counted twice under --no-renames) plus 84 reference lines in 41 files, about 175 KB; the pull request states the measured size.
Done when
The done-when lines below are copied from #12489 as written, except the first, which is narrowed to this part's skill. The Scope line names the target this part covers.
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.sh passes, and so does bash scripts/sync-shared-copies.sh --check-bump origin/main.
A merge probe is posted per D82/Q186 for each sub-slice.
Scope: skill-quality:check
Notes
Drafted by the issue-triage session. The eval is Claude subscription or promotional-credit usage, not cost (docs/contracts/loop-lane/README.md:349), so a host run makes it. Use non-Fable models for the agent and judge runs.
Proposed work class: work-class: structural
Basis: automated intake triage; the lanes App applied this class.
Size: Medium
Complexity: Medium
Uncertainty: Known
Flags: none
Blocked by: #12488
Understood: rename skill-quality:check to a distinct leaf name, chosen with /naming:name-it-better. Give its description a unique first clause, sweep references across about 41 files, and leave the skill's behavior unchanged. This is one of three renames split from #12489.
The eval-evidence item needs a host run. An unattended lane can't do that item, so it doesn't hold the rest of the issue. The other done-when items can be checked in the lane.
Cost: none flagged. Eval runs draw on prepaid or subscription credit.
I found no duplicates. #12497 and #12499 are the sibling renames for other skills.
Not admitted to the issue lane: its done-when asks for what an unattended lane run cannot perform: item 3 (a model eval run: "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 host queue (host-run); it carries host-run. Admission takes the issue once each of those is met, when intake triages it again (.github/actions/resolve-config/admission-rules.json).
Closed as not planned on the owner's decision recorded at #12489 (comment): the check leaf stays, since the only reason for the rename was the Cursor /check collision.
Activity
github-actions commentedon Nov 2, 2026
Proposed work class: work-class: structural
Basis: automated intake triage; the lanes App applied this class.
Size: Medium
Complexity: Medium
Uncertainty: Known
Flags: none
Blocked by: #12488
Understood: rename
skill-quality:checkto a distinct leaf name, chosen with/naming:name-it-better. Give its description a unique first clause, sweep references across about 41 files, and leave the skill's behavior unchanged. This is one of three renames split from #12489.The eval-evidence item needs a host run. An unattended lane can't do that item, so it doesn't hold the rest of the issue. The other done-when items can be checked in the lane.
Cost: none flagged. Eval runs draw on prepaid or subscription credit.
I found no duplicates. #12497 and #12499 are the sibling renames for other skills.
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 3 (a model eval run: "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 host queue (
host-run); it carries host-run. 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: confirmed; its comment says why.kyle-sexton commentedon Nov 3, 2026
Closed as not planned on the owner's decision recorded at #12489 (comment): the check leaf stays, since the only reason for the rename was the Cursor /check collision.