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.
12 Comments
@delexw I don't know if this will help you work around the issue, I experienced this problem as well. I seem to have been able to work around by changing the prompt content to use
Run SlashCommand(/my-command args) and then Run SlashCommand(...)instead ofrun /my-command@delexw My previous suggestion stopped working. It feels like a bug. Claude keeps blaming the stoppage on misjudging the output as as a stop signal. Though removing al explicit output doesn't solve the problem either.
This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.
Same issue here. Trying to chain two custom slash commands and a standard slash command (/clear). Stops after executing the first one.
What is the correct way to get around this? Is it a Claude Code bug, or a prompt authoring issue?
Hey guys, this is definitely a bug, or at least an oversight on Anthropic's part. Composing multiple commands worked just fine until they introduced the Skill tool. It's particularly frustrating because Claude will lie about why it stopped.
As a solution, you can disable the Skill tool entirely, and just tell it to run the commands via the file name. This works for me for composing multi-command workflows.
So in your .claude/settings.local.json, just do:
Of course, the long term solution is for Anthropic to fix the broken tool. But this should get things working again for now.
Happens to me too. Pretty frustrating.
This issue has been automatically closed due to 60 days of inactivity. If you're still experiencing this issue, please open a new issue with updated information.
You can close the ticket, but it's still and issue.
I'd love for this to work.
This issue was closed incorrectly despite recent human comments. This behavior of the bot is reported at https://github.com/anthropics/claude-code/issues/16497. Please upvote that issue, so maybe it gets noticed.
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.