command-development_skill

Overview

This skill explains how to create, organize, and run slash commands for Claude Code. It covers Markdown command format, YAML frontmatter options, dynamic arguments, file references, bash execution, and best practices for reliable, reusable commands. Use it to build consistent developer workflows that Claude can execute directly.

How this skill works

Commands are Markdown files that Claude executes when invoked; the file content becomes instructions directed to the agent. YAML frontmatter configures description, allowed tools, model selection, and argument hints. Arguments ($1, $2, $ARGUMENTS) and @ file references inject user input and file contents, while inline bash can run repository commands to gather context prior to processing. Place commands in project, user, or plugin locations to control scope and namespacing.

When to use it

• You want to create a reusable slash command for common tasks (reviews, deploys, tests).
• You need dynamic arguments or file contents inserted into a command run.
• You must run repository-level commands (git, npm) and include results in the prompt.
• You want to limit tool access or specify the model for safer, faster execution.
• You need to organize many commands into namespaces or plugin-specific sets.

Best practices

• Design single-responsibility commands with clear verb-noun names (review-pr, deploy).
• Write prompts as direct instructions to Claude, not descriptions for users.
• Document arguments with argument-hint and validate missing/invalid args inside the prompt.
• Use allowed-tools to restrict Bash scope (e.g., Bash(git:*)) and avoid destructive commands.
• Prefer explicit file paths, handle missing files gracefully, and test bash snippets locally.

Example use cases

• Review a specific pull request: /review-pr 123 — uses $1 and allowed-tools: Read, Bash(git:*).
• Run tests for a file: /test-file spec/unit/foo.test.js — uses Bash(npm:*) to run tests and analyze output.
• Deploy an app: /deploy api staging v1.2.3 — combines positional args and bash to fetch build info.
• Generate docs from a template: /generate-docs src/components/Button — includes @file references and templates.
• Compare files: /diff src/old.js src/new.js — uses multiple @ references and reports breaking changes.