Custom slash command stops after nested SlashCommand call without executing subsequent steps
Context
I have a custom slash command /github:go that orchestrates a multi-step workflow. The command is defined to execute two other slash commands in sequence: /github:commit followed by /github:create-pr.
Expected Behavior
When the custom /github:go command executes, it should:
- Pull main branch
- Create a new branch if existing branch has a PR (or use existing branch)
- Execute
/github:commitslash command using the SlashCommand tool - Continue and execute
/github:create-prslash command using the SlashCommand tool
Actual Behavior
The custom command stops after successfully executing the first SlashCommand call (/github:commit) and does not proceed to execute the second SlashCommand call (/github:create-pr). The workflow halts without completing the pull request creation step.
Steps to Reproduce
- Create a custom slash command that calls multiple slash commands sequentially using the SlashCommand tool
- Have the custom command execute SlashCommand for the first nested command (e.g.,
/github:commit) - Observe that Claude stops and does not proceed to the second SlashCommand call (e.g.,
/github:create-pr)
Environment
- Claude Code Version: Latest
- Platform: macOS (Darwin 24.6.0)
- Context: Custom slash command with sequential SlashCommand tool invocations
Additional Context
The custom /github:go command explicitly states:
"Run /github:commit slash command, and continue, Run /github:create-pr slash command"
The command successfully completes the first SlashCommand invocation but fails to continue to the second one.
Expected Fix
Claude should be able to chain multiple SlashCommand tool calls within a custom slash command definition and execute them sequentially when the prompt explicitly instructs to "continue" after the first one completes.
This issue has 12 comments on GitHub. Read the full discussion on GitHub ↗