create-command

To create Claude Code slash commands, you generate a .md file in the .claude/commands directory. This Skill automates command generation by collecting your command purpose, arguments, and optional agent links to write the required markdown template.

Automating reusable prompt templates involves defining a slash command with a specific purpose and optional $ARGUMENTS placeholders. The generated .claude/commands/{name}.md file allows Claude Code to invoke the template dynamically during workflow automation.

Yes, you can link a generated slash command to an agent. During command generation, the Skill collects optional agent mapping details to ensure your shortcut delegates domain-specific tasks like ticket tracking directly to the appropriate agent.

You use $ARGUMENTS placeholders in a Claude Code command file by defining argument expectations during command generation. The Skill writes these placeholders into the .md prompt template, allowing you to pass dynamic inputs when invoking the shortcut.

No, manual verification is unnecessary because the command generation process includes a final safety verification step. It confirms the .claude/commands/{name}.md file exists and tells you exactly where to edit or delete it.

You need to generate a dedicated slash command when you want reusable quick actions for repetitive workflows. Creating deterministic .md files ensures consistent execution for tasks like status checks or release summaries without retyping prompts.