slash-commands

# Slash Commands Reference

Create and use user-triggered prompts with `/command-name` syntax.

## When to Use

- "How do I create a slash command?"
- "What slash commands are available?"
- "Add bash to my command"
- "Use file references in commands"
- "Slash commands vs skills"

## Built-in Commands

| Command | Purpose |
|---------|---------|
| `/clear` | Clear conversation history |
| `/compact` | Compact conversation with focus |
| `/config` | Open settings interface |
| `/cost` | Show token usage |
| `/agents` | Manage sub-agents |
| `/mcp` | Manage MCP servers |
| `/memory` | Edit CLAUDE.md files |
| `/model` | Select AI model |
| `/review` | Request code review |
| `/resume` | Resume session |
| `/help` | Get usage help |

## Creating Commands

### Project Commands
```bash
mkdir -p .claude/commands
cat > .claude/commands/optimize.md << 'EOF'
---
description: Analyze code for performance issues
---

Review this code for:
- Performance bottlenecks
- Memory leaks
- Caching opportunities
EOF
```

### Personal Commands
```bash
mkdir -p ~/.claude/commands
cat > ~/.claude/commands/review.md << 'EOF'
---
description: Security-focused code review
---

Check for vulnerabilities:
- Input validation
- SQL injection
- XSS risks
EOF
```

## Command File Format

```yaml
---
description: Brief description for /help
allowed-tools: [Bash, Read, Write]  # Optional
argument-hint: "[file] [type]"       # Optional
---

Your markdown instructions here.
Use $1, $2 for arguments or $ARGUMENTS for all.
```

## Bash Execution

Run bash before loading prompt with `!` prefix:

```yaml
---
allowed-tools: Bash(git:*), Bash(grep:*)
description: Git commit helper
---

Current status: !`git status`
Staged changes: !`git diff --staged`
Recent commits: !`git log --oneline -5`

Based on these changes, suggest a commit message.
```

**Rules:**
- Must declare `allowed-tools: Bash(...)` in frontmatter
- Use backticks: `` !`command` ``
- Output is included in Claude's context

## File References

In