Our review

This skill guides users in creating custom slash commands for Claude Code using Markdown files with frontmatter configuration.

Strengths

Structured approach with clear file locations
Supports arguments and dynamic content
Allows namespacing for organizing commands
Can restrict tool access for security

Limitations

Requires precise adherence to file naming and location
Dynamic content has bugs (e.g., special characters in backticks)
Scope management between project and personal commands can be confusing

When to use it

Use this skill when you need to add reusable, custom commands to Claude Code for repetitive tasks or workflows.

When not to use it

Avoid this skill if the functionality can be achieved with a simple one-time prompt or if you need complex, stateful interactions beyond what a single command can provide.

Examples

Create a project-level slash command for code review

Create a slash command for Claude Code that reviews the current file for bugs and style issues, storing it in .claude/commands/review.md.

Add a personal slash command with arguments

Create a personal slash command `/summarize` that takes a file path as an argument and provides a summary of the file's contents.

Build a namespaced command with dynamic content

Add a command under .claude/commands/git/ that shows the current branch and recent commits using dynamic bash execution.

name: claude-code-slash-commands description: This skill should be used when the user asks to "create a command", "write a slash command", "build a plugin command", or wants to add custom commands to Claude Code. allowed-tools: Read, Grep

Slash Command Development

Create custom slash commands for Claude Code.

Quick Reference

You MUST read these references for detailed guidance:

Official Documentation - Anthropic's slash command guide

Command Structure

Commands are Markdown files in specific locations:

| Scope | Location | Description suffix | |-------|----------|-------------------| | Project | .claude/commands/ | (project) | | Personal | ~/.claude/commands/ | (user) | | Plugin | commands/ in plugin root | (plugin) |

Basic Command

---
description: Brief description of what this command does
---

Your prompt instructions here.

Frontmatter Options

---
allowed-tools: Bash(git:*), Read
argument-hint: [filename] [options]
description: What this command does
model: claude-3-5-haiku-20241022
disable-model-invocation: false
context: fork
---

| Field | Purpose | |-------|---------| | allowed-tools | Tools the command can use | | argument-hint | Shows in autocomplete (e.g., [message]) | | description | Brief description (required for SlashCommand tool) | | model | Specific model to use | | disable-model-invocation | Prevent programmatic invocation | | context: fork | Run in isolated sub-agent context, preventing side effects on main agent state |

Arguments

All arguments:

Fix issue #$ARGUMENTS following our coding standards

Positional arguments:

Review PR #$1 with priority $2 and assign to $3

Dynamic Content

Bash execution (prefix with exclamation mark):

Current branch: EXCLAMATION`git branch --show-current`
Recent commits: EXCLAMATION`git log --oneline -5`

Replace EXCLAMATION with the exclamation mark character - workaround for bug #12762.

File references (prefix with at-sign):

Review the implementation in @src/utils/helpers.js

Namespacing

Subdirectories group related commands:

.claude/commands/frontend/test.md → /test shows (project:frontend)
.claude/commands/backend/test.md → /test shows (project:backend)

Checklist

[ ] Description filled in frontmatter
[ ] argument-hint if command takes arguments
[ ] allowed-tools if using Bash or specific tools
[ ] Test with /command-name --help style invocation

Claude Code Slash Command Development

Recommended for