Creating Slash Commands

Slash commands automate workflows by encapsulating multi-step processes into reusable commands. Create a file under .claude/commands/[name].md with YAML frontmatter defining permissions (allowed-tools), a command prompt using $ARGUMENTS, and explicit decision logic. Test via /<command> [args].

Slash commands use YAML frontmatter to specify allowed-tools, controlling which CLI tools and integrations (GitHub CLI, git, custom scripts) each command can access. This enables secure automation by restricting permissions per command.

Yes. Slash commands integrate with GitHub CLI, git, and custom scripts for project automation, issue triage, and PR reviews. Define tool access in YAML frontmatter and reference them in your command prompt logic.

Structure command prompts with $ARGUMENTS placeholders for user input, explicit decision logic for multi-step workflows, and a .claude/commands model directory. This creates testable, reusable automation that handles complex workflows end-to-end.

Test slash commands by running /<command> [args] in your CLI. The command executes the prompt with specified arguments, allowing you to verify decision logic and tool integrations before deploying to production workflows.

Slash commands require familiarity with YAML syntax for permissions and CLI tools like GitHub CLI or git. You write command prompts with step-by-step logic rather than code, making automation accessible without programming expertise.