name: slash-command-creator
description: Create slash commands (reusable prompt templates). Use when building /commands, defining workflows users invoke explicitly, or setting up repeatable prompts with arguments.

Slash Command Creator

Create reusable slash commands for agent workflows.

When This Triggers

• User wants to create a /command
• User is building a reusable prompt template
• User asks about slash command syntax or arguments
• User wants to automate a repeated workflow

What Slash Commands Are

Markdown files containing reusable prompts. Define instructions once, invoke with /<name>.

Use slash commands for:
- Workflows invoked explicitly by user
- Context-sensitive operations
- Prompts with variable arguments
- Quick, repeatable tasks

Don't use slash commands for:
- Default behaviors → use AGENTS.md
- Complex multi-step with scripts → use skills

Quick Start Template

---
description: Brief description shown in help
argument-hint: [required-arg] [optional-arg]
---

## Context

[Background information, dynamic content with !`commands`]

## Task

[What to do with $ARGUMENTS or $1, $2, etc.]

File Location

Filename becomes command name (minus .md).

Arguments

Capture All: $ARGUMENTS

Fix issue #$ARGUMENTS following our standards

/fix-issue 123 urgent → $ARGUMENTS = "123 urgent"

Positional: $1, $2, $3

Review PR #$1 with priority $2

/review 456 high → $1="456", $2="high"

Dynamic Content

Shell Output: !

Current status: !`git status`
Recent commits: !`git log --oneline -5`

File Contents: @

Review @src/main.ts against @docs/spec.md

Frontmatter Options

---
allowed-tools: Bash(git:*), Read(*)
argument-hint: [issue-number]
description: Fix a GitHub issue
model: claude-3-5-sonnet
disable-model-invocation: false
---

Complete Example

---
allowed-tools: Bash(git:*)
argument-hint: [commit message]
description: Create a well-formed git commit
---

## Context

- Status: !`git status --short`
- Diff: !`git diff --cached --stat`
- Branch: !`git branch --show-current`

## Task

Create a commit with message: $ARGUMENTS

If no message provided, generate one from the staged changes.
Follow conventional commits format: type(scope): description

Best Practices

• One purpose per command: Keep focused
• Always include description: For discoverability
• Use argument-hint: Guide users on expected input
• Scope permissions: Only grant what's needed
• Keep prompts short: Link to docs instead of embedding
• Use dynamic content: ! for fresh state, @ for files

See Also

references/command-syntax.md for complete syntax reference.