command-development

This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.

19,608stars2,461forksUpdated 5/18/2026

Code Review Productivity & Workflow Documentation #slash-commands #command-development #markdown #code-review #yaml #automation

Security Assessment

High Risk(40/100)

Detected risks:

Destructive Operations([references/testing-strategies.md] dd if=, [references/marketplace-considerations.md] rm -rf)

Security Score40/100

About command-development

The command-development skill is designed to assist users in creating, organizing, and managing slash commands for Claude Code. It provides structured guidance on writing commands in Markdown format, configuring them with YAML frontmatter, and utilizing dynamic arguments and file references. By standardizing the process of command creation, this skill helps ensure that commands are clear, reusable, and executable by Claude, improving workflow efficiency and collaboration across projects.

This skill offers a variety of capabilities, including instruction on slash command structure, frontmatter options, dynamic argument usage, and Bash execution within commands. It emphasizes best practices for writing commands that are directives to Claude rather than messages to end users. Users also learn how to organize commands across different scopes, including project-specific, personal, and plugin-based commands, as well as guidance on naming conventions and file placement for maximum usability.

Target users include developers, technical writers, and teams who wish to create interactive workflows or automate repetitive tasks within Claude Code. Common use cases involve defining reusable commands for code review, testing, deployment processes, or other custom tasks. The skill benefits both individual users creating personal shortcuts and teams needing standardized, sharable command sets for collaborative projects.

FAQ

What is the recommended format for creating a new slash command?

New slash commands should be created as Markdown files, preferably in the .claude/skills/<name>/SKILL.md directory for new skills. Commands can include YAML frontmatter for configuration and can use dynamic arguments and file references.

Can commands include executable scripts like Bash?

Yes, commands can include Bash execution to provide context or perform operations. The skill covers how to integrate such scripts safely within command prompts.

Where should I place project-specific versus personal commands?

Project-specific commands go in .claude/commands/ for team use, personal commands go in ~/.claude/commands/ for availability across all projects, and plugin commands go in plugin-name/commands/.

Are there any limitations on which tools or models can be used in commands?

Commands can specify allowed tools and models in YAML frontmatter, but this depends on what is supported by Claude Code and the project setup.

How should commands be written to ensure Claude executes them correctly?

Commands should be written as instructions for Claude, not messages to the user. Focus on telling Claude exactly what to do rather than describing the output to the user.