fix: declare the release skill's argument the way skills take arguments - #112
Merged
Merged
Conversation
The bump argument was written as `$1`, which is the shape a shell script or a plugin command takes — not a skill. Claude Code's own skill-authoring guidance is explicit: `arguments` and `argument-hint` go together, and the body substitutes `$name`. Without the `arguments` declaration there was nothing to substitute and nothing to hint with, so `/release minor` offered no completion and `$1` reached the body as literal text. Declares `arguments: [bump]` and reads `$bump` throughout. Adds `when_to_use`, which is the field auto-invocation actually keys off — the description alone was carrying trigger phrases that belong there, so the phrases move and the description goes back to saying what the skill does. Verified against the frontmatter schema in the Claude Code build in use here (2.1.245), which accepts exactly: argument-hint, arguments, disable-model-invocation, user-invocable, context, agent, paths, settings. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NhcXpAA66z8a1mRJzARJqy
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
1 participant
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.
Follow-up to #111.
/release minorshowed no argument hint, because the argument was declared the wrong way.What was wrong
The bump argument was written as
$1— the shape a shell script or a plugin command takes, not a skill. Claude Code's bundled skill-authoring guidance is explicit:The skill had
argument-hintbut noarguments, so there was nothing to substitute and nothing to hint with:$1reached the body as literal text.What changed
arguments: [bump]declared, and the body reads$bumpthroughout (inputs section, step 2 prose, the shell snippet).when_to_useadded. That is the field auto-invocation keys off; the trigger phrases were sitting indescription, which should just say what the skill does. Phrases moved, description trimmed.Verification
Read the frontmatter schema out of the Claude Code build in use here (2.1.245). It accepts exactly
argument-hint,arguments,disable-model-invocation,user-invocable,context,agent,paths,settings— soargument-hintwas a valid key all along; it was the missingargumentscompanion that made it inert.🤖 Generated with Claude Code
https://claude.ai/code/session_01NhcXpAA66z8a1mRJzARJqy