fix: quote plugin paths in shell hook commands for Windows compatibility

[asafkorem]

Summary

• Fixes shell hook commands failing on Windows due to unquoted backslash paths in ${CLAUDE_PLUGIN_ROOT} substitution
• Affects: ralph-wiggum, learning-output-style, explanatory-output-style plugins
• Wraps ${CLAUDE_PLUGIN_ROOT} in double quotes and adds explicit bash prefix to prevent backslash interpretation

Problem

On Windows, ${CLAUDE_PLUGIN_ROOT} resolves to a path with backslashes (e.g., C:\Users\asafk\.claude\plugins\cache\...). When the CLI executes hook commands via cmd.exe → bash (with shell: true), unquoted backslashes are interpreted by bash as escape characters:

# What bash receives (unquoted):
bash C:\Users\asafk\.claude\plugins\cache\...\stop-hook.sh

# What bash interprets (\U→U, \a→a, \.→., etc.):
C:Usersasafk.claudepluginscache...stop-hook.sh
→ "No such file or directory"

Root cause

In the CLI's hook execution function (rZ6 in cli.js), ${CLAUDE_PLUGIN_ROOT} is replaced with the raw OS path, then the resulting command string is passed to bash without quoting:

// Template substitution with raw Windows path (backslashes)
if ($) X = X.replace(/\$\{CLAUDE_PLUGIN_ROOT\}/g, $);

// Windows .sh detection adds bash prefix
if (eA() === "windows" && X.trim().match(/\.sh(\s|$|")/)) {
  if (!X.trim().startsWith("bash ")) X = `bash ${X}`;
}

// Executed with shell: true (cmd.exe on Windows)
let P = fQY(j, [], { env: M, shell: true, windowsHide: true });

Fix

Wrap the ${CLAUDE_PLUGIN_ROOT} path in double quotes within hook commands. In bash double quotes, backslashes are only special before $, `, ", \, and newline — so \U, \a, \., \p, \c, \r, \1 are all preserved literally.

- "command": "${CLAUDE_PLUGIN_ROOT}/hooks/stop-hook.sh"
+ "command": "bash \"${CLAUDE_PLUGIN_ROOT}/hooks/stop-hook.sh\""

The explicit bash prefix:

• Prevents the CLI from double-prepending bash on Windows (it skips when command already starts with bash )
• Ensures consistent cross-platform behavior (equivalent to the #!/bin/bash shebang on Unix)

Verification

Tested on Windows 11 with Git Bash:

WIN_PATH='C:\Users\asafk\Development\claude-code\plugins\ralph-wiggum\hooks'

# BEFORE (unquoted — bug):
$ bash -c "bash ${WIN_PATH}\stop-hook.sh"
bash: C:UsersasafkDevelopmentclaude-codepluginsralph-wiggumhooksstop-hook.sh: No such file or directory

# AFTER (quoted — fix):
$ bash -c "bash \"${WIN_PATH}\stop-hook.sh\""
(exit code: 0)  # Script runs successfully

Also verified Unix-style forward-slash paths are unaffected.

Test plan

• Reproduced original error on Windows 11 with Git Bash
• Verified fix: quoted path preserves backslashes in bash double quotes
• Verified no regression: Unix forward-slash paths work unchanged
• Validated all 3 modified JSON files parse correctly
• Manual test: install ralph-wiggum plugin on Windows and run /ralph-loop
• Manual test: install learning-output-style plugin on Windows
• Manual test: install explanatory-output-style plugin on Windows

🤖 Generated with Claude Code