Repository navigation
Add typed trigger phrases (tdd, systematic debug) and sibling cross-routes to debugging/TDD descriptions - #2229
Closed
BrotherPanan wants to merge 1 commit into
Closed
BrotherPanan wants to merge 1 commit into
BrotherPanan wants to merge 1 commit into
Conversation
…criptions "tdd", "tdd workflow", "red green refactor", "systematic debug" and similar short forms users actually type now anchor to the right skill, and each description routes the confusable case to its sibling. Original clauses preserved verbatim; WHEN-only per writing-skills description doctrine. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VjSrPcwcqBA71tTGZGBVDf
obra
added
skill:systematic-debugging
Owner
|
Hi @BrotherPanan! I'm Claude, helping @obra triage. Skill descriptions are tuned deliberately and the routing claim comes without data. Changes to skill wording shape agent behavior, so they need eval evidence (see "Skill Changes Require Evaluation" in CLAUDE.md). Closing it isn't a judgment about you or your work; we're clearing out PRs against — Claude (Opus 5.5, |
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
2 participants
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.
What
Adds typed short-form trigger phrases to two skill descriptions, plus a cross-route to the confusable sibling:
systematic-debugging: + "systematic debug", "debug this properly", "find the root cause first"; routes new-behavior work to test-driven-development.test-driven-development: + "tdd", "tdd workflow", "write the test first", "red green refactor"; routes existing-defect work to systematic-debugging.Both keep the original description clause verbatim and stay WHEN-only per writing-skills' own description doctrine (no what-it-does, no workflow summary, well under 500 chars).
Why
We run a large multi-skill Claude Code environment (300+ skills/commands) and measured skill routing over an extended session corpus. Users who type the common short forms — "tdd" being the clearest case — did not route to these skills: the current descriptions describe the situation but not the phrases people actually type, and nothing in either description separates the pair (new behavior test-first vs existing defect), so bare "tdd"/"debug this properly" utterances had no anchor.
Scope kept deliberately minimal: description-only, original clauses preserved, no body changes.
🤖 Generated with Claude Code
https://claude.ai/code/session_01VjSrPcwcqBA71tTGZGBVDf