Slash commands from bundled skills now support arguments, completions, background runs and effort settings.
What's wrong with this entry?
Slash commands generated from bundled plugin skills now carry through a much larger set of command features, so they behave more like hand-written commands.
- Newly passed through:
argsMayContainSlashCommands,getContext,background, the resolvedskillRoot,getEffort,getDefaultEffort,onUserTypedArgsandgetArgumentCompletions. - A skill-supplied
progressMessageis forwarded, defaulting to "running". - getPromptForCommand now comes from a cached wireSkillFilesExtraction step.
argsMayContainSlashCommands
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
A crashing slash command now tells you it crashed
Both mention slash command
-
v2.1.234
A command can decide from its arguments whether it counts as sensitive
Both mention slash command
-
v2.1.234
A slash-command grouping for a command that does not exist
Both mention slash command