Relocate reviewer-pinning out of the shared model-tiers block (v2.24.1) - #5
Merged
Merged
Conversation
The shared model-tiers map bundled two things with different audiences and inlined the whole bundle into all five skills: Tier classification (needed by every skill, which each classify their own model) and Reviewer pinning by host (consumed only by /evaluate). That put ~30 lines of /evaluate-voiced pinning instructions into /case, /refine, /solve, and /orchestrate — dead weight addressed to the wrong skill. Shrink shared/model-tiers.md to Tier classification only (still synced into all five by model-tiers-sync.sh). Move Reviewer pinning by host into evaluate/SKILL.md as native prose — its sole consumer, and its step 4b.1 already points at it — and drop the redundant host table in favor of the capability-keyed branch list it duplicated. Fix the now-stale "in the Model Tiers section above" cross-reference. No behavior change: the pinning logic is identical, just relocated and de-duplicated. Bumps: plugin/marketplace 2.24.0 -> 2.24.1 (all four manifests); /case 2.10.1, /refine 1.9.1, /orchestrate 1.5.1, /solve 1.7.1, /evaluate 1.14.1. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
shared/model-tiers.mdbundled two things with different audiences and inlined the whole bundle into all five skills:/evaluate, written as/evaluate("/evaluate's request-changes path must…").So
/case,/refine,/solve, and/orchestrateeach carried ~30 lines of/evaluate-voiced pinning instructions they never reference — dead weight addressed to the wrong skill.Change
shared/model-tiers.md→ Tier classification only. Still synced into all five skills bymodel-tiers-sync.sh.evaluate/SKILL.mdas native prose — its sole consumer, and its step 4b.1 already points at it."in the Model Tiers section above"cross-reference.No behavior change — the pinning logic is identical, just relocated and de-duplicated. Intra-
/evaluateredundancy between the native map and step 4b.1's operational detail was reviewed and intentionally left (local redundancy on the execution hard path).Bumps
Plugin/marketplace
2.24.0 → 2.24.1(all four manifests);/case2.10.1,/refine1.9.1,/orchestrate1.5.1,/solve1.7.1,/evaluate1.14.1.Verification
model-tiers-sync.sh+rubrics-sync.sh: no driftmodel-guard.shnot run — no Model Guard prose touched🤖 Generated with Claude Code