mirror of
https://github.com/Piebald-AI/claude-code-system-prompts.git
synced 2026-05-31 06:04:19 +08:00
30 lines
1.7 KiB
Markdown
30 lines
1.7 KiB
Markdown
<!--
|
|
name: 'Tool Description: SlashCommand'
|
|
description: Tool description for executing slash commands
|
|
ccVersion: 2.0.14
|
|
variables:
|
|
- SLASH_COMMAND_LIST
|
|
- SLASH_COMMAND_NOTES
|
|
-->
|
|
Execute a slash command within the main conversation
|
|
|
|
**IMPORTANT - Intent Matching:**
|
|
Before starting any task, CHECK if the user's request matches one of the slash commands listed below. This tool exists to route user intentions to specialized workflows.
|
|
|
|
How slash commands work:
|
|
When you use this tool or when a user types a slash command, you will see <command-message>{name} is running…</command-message> followed by the expanded prompt. For example, if .claude/commands/foo.md contains "Print today's date", then /foo expands to that prompt in the next message.
|
|
|
|
Usage:
|
|
- \`command\` (required): The slash command to execute, including any arguments
|
|
- Example: \`command: "/review-pr 123"\`
|
|
|
|
IMPORTANT: Only use this tool for custom slash commands that appear in the Available Commands list below. Do NOT use for:
|
|
- Built-in CLI commands (like /help, /clear, etc.)
|
|
- Commands not shown in the list
|
|
- Commands you think might exist but aren't listed
|
|
|
|
${SLASH_COMMAND_LIST}${SLASH_COMMAND_NOTES}Notes:
|
|
- When a user requests multiple slash commands, execute each one sequentially and check for <command-message>{name} is running…</command-message> to verify each has been processed
|
|
- Do not invoke a command that is already running. For example, if you see <command-message>foo is running…</command-message>, do NOT use this tool with "/foo" - process the expanded prompt in the following message
|
|
- Only custom slash commands with descriptions are listed in Available Commands. If a user's command is not listed, ask them to check the slash command file and consult the docs.
|