Slash commands

Control Claude's behavior during an interactive session with slash commands.

Built-in slash commands

Command	Purpose
`/add-dir`	Add additional working directories
`/agents`	Manage custom AI subagents for specialized tasks
`/bashes`	List and manage background tasks
`/bug`	Report bugs (sends conversation to Anthropic)
`/clear`	Clear conversation history
`/compact [instructions]`	Compact conversation with optional focus instructions
`/config`	Open the Settings interface (Config tab)
`/context`	Visualize current context usage as a colored grid
`/cost`	Show token usage statistics. See cost tracking guide for subscription-specific details.
`/doctor`	Checks the health of your Claude Code installation
`/exit`	Exit the REPL
`/export [filename]`	Export the current conversation to a file or clipboard
`/help`	Get usage help
`/hooks`	Manage hook configurations for tool events
`/ide`	Manage IDE integrations and show status
`/init`	Initialize project with `CLAUDE.md` guide
`/install-github-app`	Set up Claude GitHub Actions for a repository
`/login`	Switch Anthropic accounts
`/logout`	Sign out from your Anthropic account
`/mcp`	Manage MCP server connections and OAuth authentication
`/memory`	Edit `CLAUDE.md` memory files
`/model`	Select or change the AI model
`/output-style [style]`	Set the output style directly or from a selection menu
`/permissions`	View or update permissions
`/plan`	Enter plan mode directly from the prompt
`/plugin`	Manage Claude Code plugins
`/pr-comments`	View pull request comments
`/privacy-settings`	View and update your privacy settings
`/release-notes`	View release notes
`/rename <name>`	Rename the current session for easier identification
`/remote-env`	Configure remote session environment (claude.ai subscribers)
`/resume [session]`	Resume a conversation by ID or name, or open the session picker
`/review`	Request code review
`/rewind`	Rewind the conversation and/or code
`/sandbox`	Enable sandboxed bash tool with filesystem and network isolation for safer, more autonomous execution
`/security-review`	Complete a security review of pending changes on the current branch
`/stats`	Visualize daily usage, session history, streaks, and model preferences
`/status`	Open the Settings interface (Status tab) showing version, model, account, and connectivity
`/statusline`	Set up Claude Code's status line UI
`/teleport`	Resume a remote session from claude.ai by session ID, or open a picker (claude.ai subscribers)
`/terminal-setup`	Install Shift+Enter key binding for newlines (VS Code, Alacritty, Zed, Warp)
`/theme`	Change the color theme
`/todos`	List current TODO items
`/usage`	For subscription plans only: show plan usage limits and rate limit status
`/vim`	Enter vim mode for alternating insert and command modes

Custom slash commands

Custom slash commands allow you to define frequently used prompts as Markdown files that Claude Code can execute. Commands are organized by scope (project-specific or personal) and support namespacing through directory structures.

Syntax

/<command-name> [arguments]

Parameters

Parameter	Description
`<command-name>`	Name derived from the Markdown filename (without `.md` extension)
`[arguments]`	Optional arguments passed to the command

Command types

Project commands

Commands stored in your repository and shared with your team. When listed in /help, these commands show "(project)" after their description.

Location: .claude/commands/

The following example creates the /optimize command:

# Create a project command
mkdir -p .claude/commands
echo "Analyze this code for performance issues and suggest optimizations:" > .claude/commands/optimize.md

Personal commands

Commands available across all your projects. When listed in /help, these commands show "(user)" after their description.

Location: ~/.claude/commands/

The following example creates the /security-review command:

# Create a personal command
mkdir -p ~/.claude/commands
echo "Review this code for security vulnerabilities:" > ~/.claude/commands/security-review.md

Features

Namespacing

Use subdirectories to group related commands. Subdirectories appear in the command description but don't affect the command name.

For example:

.claude/commands/frontend/component.md creates /component with description "(project:frontend)"
~/.claude/commands/component.md creates /component with description "(user)"

If a project command and user command share the same name, the project command takes precedence and the user command is silently ignored. For example, if both .claude/commands/deploy.md and ~/.claude/commands/deploy.md exist, /deploy runs the project version.

Commands in different subdirectories can share names since the subdirectory appears in the description to distinguish them. For example, .claude/commands/frontend/test.md and .claude/commands/backend/test.md both create /test, but show as "(project:frontend)" and "(project:backend)" respectively.

Arguments

Pass dynamic values to commands using argument placeholders:

All arguments with `$ARGUMENTS`

The $ARGUMENTS placeholder captures all arguments passed to the command:

# Command definition
echo 'Fix issue #$ARGUMENTS following our coding standards' > .claude/commands/fix-issue.md

# Usage
> /fix-issue 123 high-priority
# $ARGUMENTS becomes: "123 high-priority"

Individual arguments with `$1`, `$2`, etc.

Access specific arguments individually using positional parameters (similar to shell scripts):

# Command definition  
echo 'Review PR #$1 with priority $2 and assign to $3' > .claude/commands/review-pr.md

# Usage
> /review-pr 456 high alice
# $1 becomes "456", $2 becomes "high", $3 becomes "alice"

Use positional arguments when you need to:

Access arguments individually in different parts of your command
Provide defaults for missing arguments
Build more structured commands with specific parameter roles

Bash command execution

Execute bash commands before the slash command runs using the ! prefix. The output is included in the command context. You must include allowed-tools with the Bash tool, but you can choose the specific bash commands to allow.

For example:

---
allowed-tools: Bash(git add:*), Bash(git status:*), Bash(git commit:*)
description: Create a git commit
---

## Context

- Current git status: !`git status`
- Current git diff (staged and unstaged changes): !`git diff HEAD`
- Current branch: !`git branch --show-current`
- Recent commits: !`git log --oneline -10`

## Your task

Based on the above changes, create a single git commit.

File references

Include file contents in commands using the @ prefix to reference files.

For example:

# Reference a specific file

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

# Reference multiple files

Compare @src/old-version.js with @src/new-version.js

Thinking mode

Slash commands can trigger extended thinking by including extended thinking keywords.

Frontmatter

Command files support frontmatter, useful for specifying metadata about the command:

Frontmatter	Purpose	Default
`allowed-tools`	List of tools the command can use	Inherits from the conversation
`argument-hint`	The arguments expected for the slash command. Example: `argument-hint: add [tagId] \| remove [tagId] \| list`. This hint is shown to the user when auto-completing the slash command.	None
`description`	Brief description of the command	Uses the first line from the prompt
`model`	Specific model string (see Models overview)	Inherits from the conversation
`disable-model-invocation`	Whether to prevent the `Skill` tool from calling this command	false
`hooks`	Define hooks scoped to this command's execution. See Define hooks for commands.	None

For example:

---
allowed-tools: Bash(git add:*), Bash(git status:*), Bash(git commit:*)
argument-hint: [message]
description: Create a git commit
model: claude-3-5-haiku-20241022
---

Create a git commit with message: $ARGUMENTS

Example using positional arguments:

---
argument-hint: [pr-number] [priority] [assignee]
description: Review pull request
---

Review PR #$1 with priority $2 and assign to $3.
Focus on security, performance, and code style.

Define hooks for commands

Slash commands can define hooks that run during the command's execution. Use the hooks field to specify PreToolUse, PostToolUse, or Stop handlers:

---
description: Deploy to staging with validation
hooks:
  PreToolUse:
    - matcher: "Bash"
      hooks:
        - type: command
          command: "./scripts/validate-deploy.sh"
          once: true
---

Deploy the current branch to staging environment.

The once: true option runs the hook only once per session. After the first successful execution, the hook is removed.

Hooks defined in a command are scoped to that command's execution and are automatically cleaned up when the command finishes.

See Hooks for the complete hook configuration format.

Plugin commands

Plugins can provide custom slash commands that integrate seamlessly with Claude Code. Plugin commands work exactly like user-defined commands but are distributed through plugin marketplaces.

How plugin commands work

Plugin commands are:

Namespaced: Commands can use the format /plugin-name:command-name to avoid conflicts (plugin prefix is optional unless there are name collisions)
Automatically available: Once a plugin is installed and enabled, its commands appear in /help
Fully integrated: Support all command features (arguments, frontmatter, bash execution, file references)

Plugin command structure

Location: commands/ directory in plugin root

File format: Markdown files with frontmatter

Basic command structure:

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

# Command Name

Detailed instructions for Claude on how to execute this command.
Include specific guidance on parameters, expected outcomes, and any special considerations.

Advanced command features:

Arguments: Use placeholders like {arg1} in command descriptions
Subdirectories: Organize commands in subdirectories for namespacing
Bash integration: Commands can execute shell scripts and programs
File references: Commands can reference and modify project files

Invocation patterns

/command-name

/plugin-name:command-name

/command-name arg1 arg2

MCP slash commands

MCP servers can expose prompts as slash commands that become available in Claude Code. These commands are dynamically discovered from connected MCP servers.

Command format

MCP commands follow the pattern:

/mcp__<server-name>__<prompt-name> [arguments]

Features

Dynamic discovery

MCP commands are automatically available when:

An MCP server is connected and active
The server exposes prompts through the MCP protocol
The prompts are successfully retrieved during connection

Arguments

MCP prompts can accept arguments defined by the server:

# Without arguments
> /mcp__github__list_prs

# With arguments
> /mcp__github__pr_review 456
> /mcp__jira__create_issue "Bug title" high

Naming conventions

Server and prompt names are normalized:

Spaces and special characters become underscores
Names are lowercase for consistency

Managing MCP connections

Use the /mcp command to:

View all configured MCP servers
Check connection status
Authenticate with OAuth-enabled servers
Clear authentication tokens
View available tools and prompts from each server

MCP permissions and wildcards

To approve all tools from an MCP server, use either the server name alone or wildcard syntax:

mcp__github (approves all GitHub tools)
mcp__github__* (wildcard syntax, also approves all GitHub tools)

To approve specific tools, list each one explicitly:

mcp__github__get_issue
mcp__github__list_issues

See MCP permission rules for more details.

`Skill` tool

The Skill tool allows Claude to programmatically invoke both custom slash commands and Agent Skills during a conversation. This gives Claude the ability to use these capabilities on your behalf when appropriate.

What the `Skill` tool can invoke

The Skill tool provides access to:

Type	Location	Requirements
Custom slash commands	`.claude/commands/` or `~/.claude/commands/`	Must have `description` frontmatter
Agent Skills	`.claude/skills/` or `~/.claude/skills/`	Must not have `disable-model-invocation: true`

Built-in commands like /compact and /init are not available through this tool.

Encourage Claude to use specific commands

To encourage Claude to use the Skill tool, reference the command by name, including the slash, in your prompts or CLAUDE.md file:

> Run /write-unit-test when you are about to start writing tests.

This tool puts each available command's metadata into context up to the character budget limit. Use /context to monitor token usage.

To see which commands and Skills are available to the Skill tool, run claude --debug and trigger a query.

Disable the `Skill` tool

To prevent Claude from programmatically invoking any commands or Skills:

/permissions
# Add to deny rules: Skill

This removes the Skill tool and all command/Skill descriptions from context.

Disable specific commands or Skills

To prevent a specific command or Skill from being invoked programmatically via the Skill tool, add disable-model-invocation: true to its frontmatter. This also removes the item's metadata from context.

`Skill` permission rules

The permission rules support:

Exact match: Skill(/commit) (allows only /commit with no arguments)
Prefix match: Skill(/review-pr:*) (allows /review-pr with any arguments)

Character budget limit

The Skill tool includes a character budget to limit context usage. This prevents token overflow when many commands and Skills are available.

The budget includes each item's name, arguments, and description.

Default limit: 15,000 characters
Custom limit: Set via SLASH_COMMAND_TOOL_CHAR_BUDGET environment variable. The name is retained for backwards compatibility.

When the budget is exceeded, Claude sees only a subset of available items. In /context, a warning shows how many are included.

Skills vs slash commands

Slash commands and Agent Skills serve different purposes in Claude Code:

Use slash commands for

Quick, frequently used prompts:

Simple prompt snippets you use often
Quick reminders or templates
Frequently used instructions that fit in one file

Examples:

/review → "Review this code for bugs and suggest improvements"
/explain → "Explain this code in simple terms"
/optimize → "Analyze this code for performance issues"

Use Skills for

Comprehensive capabilities with structure:

Complex workflows with multiple steps
Capabilities requiring scripts or utilities
Knowledge organized across multiple files
Team workflows you want to standardize

Examples:

PDF processing Skill with form-filling scripts and validation
Data analysis Skill with reference docs for different data types
Documentation Skill with style guides and templates

Key differences

Aspect	Slash Commands	Agent Skills
Complexity	Simple prompts	Complex capabilities
Structure	Single .md file	Directory with SKILL.md + resources
Discovery	Explicit invocation (`/command`)	Automatic (based on context)
Files	One file only	Multiple files, scripts, templates
Scope	Project or personal	Project or personal
Sharing	Via git	Via git

Example comparison

As a slash command:

# .claude/commands/review.md
Review this code for:
- Security vulnerabilities
- Performance issues
- Code style violations

Usage: /review (manual invocation)

As a Skill:

.claude/skills/code-review/
├── SKILL.md (overview and workflows)
├── SECURITY.md (security checklist)
├── PERFORMANCE.md (performance patterns)
├── STYLE.md (style guide reference)
└── scripts/
    └── run-linters.sh

Usage: "Can you review this code?" (automatic discovery)

The Skill provides richer context, validation scripts, and organized reference material.

When to use each

Use slash commands:

You invoke the same prompt repeatedly
The prompt fits in a single file
You want explicit control over when it runs

Use Skills:

Claude should discover the capability automatically
Multiple files or scripts are needed
Complex workflows with validation steps
Team needs standardized, detailed guidance

Both slash commands and Skills can coexist. Use the approach that fits your needs.

Learn more about Agent Skills.

slash-commands.md +74 −34

30| `/model` | Select or change the AI model |30| `/model` | Select or change the AI model |

31| `/output-style [style]` | Set the output style directly or from a selection menu |31| `/output-style [style]` | Set the output style directly or from a selection menu |

32| `/permissions` | View or update [permissions](/en/iam#configuring-permissions) |32| `/permissions` | View or update [permissions](/en/iam#configuring-permissions) |

33| `/plan` | Enter plan mode directly from the prompt |

33| `/plugin` | Manage Claude Code plugins |34| `/plugin` | Manage Claude Code plugins |

34| `/pr-comments` | View pull request comments |35| `/pr-comments` | View pull request comments |

35| `/privacy-settings` | View and update your privacy settings |36| `/privacy-settings` | View and update your privacy settings |

36| `/release-notes` | View release notes |37| `/release-notes` | View release notes |

37| `/rename <name>` | Rename the current session for easier identification |38| `/rename <name>` | Rename the current session for easier identification |

39| `/remote-env` | Configure remote session environment (claude.ai subscribers) |

38| `/resume [session]` | Resume a conversation by ID or name, or open the session picker |40| `/resume [session]` | Resume a conversation by ID or name, or open the session picker |

39| `/review` | Request code review |41| `/review` | Request code review |

40| `/rewind` | Rewind the conversation and/or code |42| `/rewind` | Rewind the conversation and/or code |

43| `/stats` | Visualize daily usage, session history, streaks, and model preferences |45| `/stats` | Visualize daily usage, session history, streaks, and model preferences |

44| `/status` | Open the Settings interface (Status tab) showing version, model, account, and connectivity |46| `/status` | Open the Settings interface (Status tab) showing version, model, account, and connectivity |

45| `/statusline` | Set up Claude Code's status line UI |47| `/statusline` | Set up Claude Code's status line UI |

49| `/terminal-setup` | Install Shift+Enter key binding for newlines (VS Code, Alacritty, Zed, Warp) |

50| `/theme` | Change the color theme |

47| `/todos` | List current TODO items |51| `/todos` | List current TODO items |

48| `/usage` | For subscription plans only: show plan usage limits and rate limit status |52| `/usage` | For subscription plans only: show plan usage limits and rate limit status |

49| `/vim` | Enter vim mode for alternating insert and command modes |53| `/vim` | Enter vim mode for alternating insert and command modes |

52 56

53Custom slash commands allow you to define frequently used prompts as Markdown files that Claude Code can execute. Commands are organized by scope (project-specific or personal) and support namespacing through directory structures.57Custom slash commands allow you to define frequently used prompts as Markdown files that Claude Code can execute. Commands are organized by scope (project-specific or personal) and support namespacing through directory structures.

54 58

59<Tip>

60 Slash command autocomplete works anywhere in your input, not just at the beginning. Type `/` at any position to see available commands.

61</Tip>

55### Syntax63### Syntax

56 64

57```65```

212| `hooks` | Define hooks scoped to this command's execution. See [Define hooks for commands](#define-hooks-for-commands). | None |

204 213

205For example:214For example:

206 215

227Focus on security, performance, and code style.236Focus on security, performance, and code style.

228```237```

229 238

239#### Define hooks for commands

240

241Slash commands can define hooks that run during the command's execution. Use the `hooks` field to specify `PreToolUse`, `PostToolUse`, or `Stop` handlers:

242

243```markdown theme={null}

244---

245description: Deploy to staging with validation

246hooks:

247 PreToolUse:

248 - matcher: "Bash"

249 hooks:

250 - type: command

251 command: "./scripts/validate-deploy.sh"

252 once: true

253---

254

255Deploy the current branch to staging environment.

256```

257

258The `once: true` option runs the hook only once per session. After the first successful execution, the hook is removed.

259

260Hooks defined in a command are scoped to that command's execution and are automatically cleaned up when the command finishes.

261

262See [Hooks](/en/hooks) for the complete hook configuration format.

263

230## Plugin commands264## Plugin commands

231 265

232[Plugins](/en/plugins) can provide custom slash commands that integrate seamlessly with Claude Code. Plugin commands work exactly like user-defined commands but are distributed through [plugin marketplaces](/en/plugin-marketplaces).266[Plugins](/en/plugins) can provide custom slash commands that integrate seamlessly with Claude Code. Plugin commands work exactly like user-defined commands but are distributed through [plugin marketplaces](/en/plugin-marketplaces).

345 379

346See [MCP permission rules](/en/iam#tool-specific-permission-rules) for more details.380See [MCP permission rules](/en/iam#tool-specific-permission-rules) for more details.

347 381

348## `SlashCommand` tool382## `Skill` tool

349 383

350The `SlashCommand` tool allows Claude to execute [custom slash commands](/en/slash-commands#custom-slash-commands) programmatically384<Note>

351during a conversation. This gives Claude the ability to invoke custom commands385 In earlier versions of Claude Code, slash command invocation was provided by a separate `SlashCommand` tool. This has been merged into the `Skill` tool. If you have existing permission rules using `SlashCommand`, update them to use `Skill`.

352on your behalf when appropriate.386</Note>

353 387

354To encourage Claude to use the `SlashCommand` tool, reference the command by name, including the slash, in your prompts or `CLAUDE.md` file. For example:388The `Skill` tool allows Claude to programmatically invoke both [custom slash commands](/en/slash-commands#custom-slash-commands) and [Agent Skills](/en/skills) during a conversation. This gives Claude the ability to use these capabilities on your behalf when appropriate.

355 389

356```390### What the `Skill` tool can invoke

357> Run /write-unit-test when you are about to start writing tests.391

358```392The `Skill` tool provides access to:

359 393

360This tool puts each available custom slash command's metadata into context up to the character budget limit. You can use `/context` to monitor token usage and follow the operations below to manage context.394| Type | Location | Requirements |

395| :-------------------- | :------------------------------------------- | :--------------------------------------------- |

396| Custom slash commands | `.claude/commands/` or `~/.claude/commands/` | Must have `description` frontmatter |

397| Agent Skills | `.claude/skills/` or `~/.claude/skills/` | Must not have `disable-model-invocation: true` |

361 398

362### `SlashCommand` tool supported commands399Built-in commands like `/compact` and `/init` are *not* available through this tool.

363 400

364`SlashCommand` tool only supports custom slash commands that:401### Encourage Claude to use specific commands

402

403To encourage Claude to use the `Skill` tool, reference the command by name, including the slash, in your prompts or `CLAUDE.md` file:

404

405```

406> Run /write-unit-test when you are about to start writing tests.

407```

365 408

366* Are user-defined. Built-in commands like `/compact` and `/init` are *not* supported.409This tool puts each available command's metadata into context up to the character budget limit. Use `/context` to monitor token usage.

367* Have the `description` frontmatter field populated. The description is used in the context.

368 410

369For Claude Code versions >= 1.0.124, you can see which custom slash commands411To see which commands and Skills are available to the `Skill` tool, run `claude --debug` and trigger a query.

370`SlashCommand` tool can invoke by running `claude --debug` and triggering a query.

371 412

372### Disable `SlashCommand` tool413### Disable the `Skill` tool

373 414

374To prevent Claude from executing any slash commands via the tool:415To prevent Claude from programmatically invoking any commands or Skills:

375 416

376```bash theme={null}417```bash theme={null}

377/permissions418/permissions

378# Add to deny rules: SlashCommand419# Add to deny rules: Skill

379```420```

380 421

381This also removes the SlashCommand tool and command descriptions from context.422This removes the `Skill` tool and all command/Skill descriptions from context.

382 423

383### Disable specific commands only424### Disable specific commands or Skills

384 425

385To prevent a specific slash command from becoming available, add426To prevent a specific command or Skill from being invoked programmatically via the `Skill` tool, add `disable-model-invocation: true` to its frontmatter. This also removes the item's metadata from context.

386`disable-model-invocation: true` to the slash command's frontmatter.

387 427

388This also removes the command's metadata from context.428<Note>

429 The `user-invocable` field in Skills only controls menu visibility, not `Skill` tool access. Use `disable-model-invocation: true` to block programmatic invocation. See [Control Skill visibility](/en/skills#control-skill-visibility) for details.

430</Note>

389 431

390### `SlashCommand` permission rules432### `Skill` permission rules

391 433

392The permission rules support:434The permission rules support:

393 435

394* **Exact match**: `SlashCommand:/commit` (allows only `/commit` with no arguments)436* **Exact match**: `Skill(/commit)` (allows only `/commit` with no arguments)

395* **Prefix match**: `SlashCommand:/review-pr:*` (allows `/review-pr` with any arguments)437* **Prefix match**: `Skill(/review-pr:*)` (allows `/review-pr` with any arguments)

396 438

397### Character budget limit439### Character budget limit

398 440

399The `SlashCommand` tool includes a character budget to limit the size of command441The `Skill` tool includes a character budget to limit context usage. This prevents token overflow when many commands and Skills are available.

400descriptions shown to Claude. This prevents token overflow when many commands

401are available.

402 442

403The budget includes each custom slash command's name, arguments, and description.443The budget includes each item's name, arguments, and description.

404 444

405* **Default limit**: 15,000 characters445* **Default limit**: 15,000 characters

406* **Custom limit**: Set via `SLASH_COMMAND_TOOL_CHAR_BUDGET` environment variable446* **Custom limit**: Set via `SLASH_COMMAND_TOOL_CHAR_BUDGET` environment variable. The name is retained for backwards compatibility.

407 447

408When the character budget is exceeded, Claude sees only a subset of the available commands. In `/context`, a warning shows "M of N commands".448When the budget is exceeded, Claude sees only a subset of available items. In `/context`, a warning shows how many are included.

409 449

410## Skills vs slash commands450## Skills vs slash commands

411 451

slash-commands.md 2026-01-07 21:01 UTC to 2026-01-08 21:02 UTC

Slash commands

Built-in slash commands

Custom slash commands

Syntax

Parameters

Command types

Project commands

Personal commands

Features

Namespacing

Arguments

All arguments with $ARGUMENTS

Individual arguments with $1, $2, etc.

Bash command execution

File references

Thinking mode

Frontmatter

Define hooks for commands

Plugin commands

How plugin commands work

Plugin command structure

Invocation patterns

MCP slash commands

Command format

Features

Dynamic discovery

Arguments

Naming conventions

Managing MCP connections

MCP permissions and wildcards

Skill tool

What the Skill tool can invoke

Encourage Claude to use specific commands

Disable the Skill tool

Disable specific commands or Skills

Skill permission rules

Character budget limit

Skills vs slash commands

Use slash commands for

Use Skills for

Key differences

Example comparison

When to use each

See also

All arguments with `$ARGUMENTS`

Individual arguments with `$1`, `$2`, etc.

`Skill` tool

What the `Skill` tool can invoke

Disable the `Skill` tool

`Skill` permission rules