command-creator

Author Claude Code slash commands with structured arguments and approval gates.

3|Updated May 11, 2026
One-click install
npx skills add https://github.com/anilcancakir/claude-code --skill command-creator-anilcancakir
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: command-creator
Source: https://github.com/anilcancakir/claude-code/tree/main/plugins/ac/skills/command-creator
Command: npx skills add https://github.com/anilcancakir/claude-code --skill command-creator-anilcancakir

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This Skill helps you author Claude Code slash commands correctly and safely by providing a structured playbook for arguments, shell-based context gathering, approval gates, and the right command file shape.

Core Features & Use Cases

  • Command authoring guidance: designs how /name [args] becomes a working markdown-driven prompt.
  • Argument & input structuring: choose free-form, positional, or named argument patterns and ensure substitutions match.
  • Shell injection context gathering: safely inline live state (like git diffs/PR data/env) using the correct preprocessing patterns and permission expectations.
  • Phase-based command bodies: templates multi-step workflows (context, planning, approval, execution, reporting) so the model follows reliably.
  • Safety & destructive-action guardrails: inserts approval gates (AskUserQuestion) and documents error handling.

Quick Start

Use command-creator when you need to design a new Claude Code slash command (for example, to gather git/PR context and then ask for approval before running a side-effecting action).

Frequently Asked Questions about command-creator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a Claude Code slash command with arguments?

To create a Claude Code slash command, you author a markdown file with YAML frontmatter containing name and description, then define argument patterns and phase-structured workflow bodies that align with Claude Code loaders for argument substitution and prompt preprocessing.

What is shell injection context gathering in Claude Code commands?

Shell injection context gathering safely inlines live state like git diffs, PR data, or environment variables into a slash command prompt using correct preprocessing patterns, ensuring the model receives real-time context before executing side-effecting actions.

How do I add approval gates to Claude Code slash commands?

You add approval gates to slash commands by inserting AskUserQuestion prompts within the command body, ensuring the model pauses for user confirmation before running any destructive or side-effecting shell commands during the workflow execution phase.

How do I structure a multi-phase workflow in a Claude Code command file?

You structure a multi-phase workflow by templating the command body into context gathering, planning, approval, execution, and reporting phases, so the model reliably follows each step and prompts for user input at the correct stages.

Where should Claude Code slash command markdown files be stored?

Claude Code slash command markdown files should be stored under the commands/ directory or within skill directories at skills/<name>/SKILL.md, ensuring the YAML frontmatter metadata remains discoverable by the Claude Code loaders.

Can I use named arguments instead of positional arguments in Claude Code commands?

Yes, you can choose free-form, positional, or named argument patterns when authoring slash commands, ensuring the argument substitutions in the markdown body match the selected pattern and align with the Claude Code preprocessing expectations.