Git commit commands blocked despite slash command permissions

Description

When using a slash command that grants git permissions through allowed-tools, git commit commands are being blocked with the error "The user doesn't want to proceed with this tool use" even though the user has explicitly stated that the slash command provides these permissions.

Steps to Reproduce

1. Create a slash command that includes git operations in its workflow
2. Configure the slash command with appropriate allowed-tools that should permit git commits
3. Run the slash command and attempt to execute a git commit as part of the workflow
4. Observe that the git commit is blocked despite having permissions

Expected Behavior

• Git commands (including commits) should execute successfully when permissions are granted through slash command allowed-tools
• No permission prompts should appear for operations that are explicitly allowed by the slash command

Actual Behavior

• Git commit commands are blocked with error: "The user doesn't want to proceed with this tool use"
• This occurs even when the user confirms that the slash command grants these permissions
• The blocking persists across multiple attempts

Impact

This prevents slash commands from completing automated workflows that require git commits, forcing users to manually intervene to complete operations that should be automated.

Environment

• Claude Code version: Latest
• Platform: macOS (Darwin 24.4.0)
• Context: Within a slash command that has git permissions in its allowed-tools configuration