Problem: SessionStart hook error after installing superpowers —— Trove problem library

What you will run into

After install, Claude Code reports a hook error on startup (SessionStart hook failed). You think it installed wrong; reinstalling still errors.

Why this happens

Two common root causes:

Hooks are not run by the plugin itself — Claude Code executes them on the plugin's behalf at session startup: it reads the hook declaration in the plugin config, resolves the path to session-start.sh, and launches the script.

So a hook error has two completely different causes: the script itself is broken (syntax / missing dependency), or Claude Code cannot find/execute the path (the Windows path-handling bug is this class).

Running bash session-start.sh manually matters because it bypasses the launcher and validates the script directly: manual run OK = launcher/path problem (upgrade or switch form); manual run also errors = script problem (fix the script).

One step separates the two causes.

Step by step

1. Upgrade Claude Code and the plugin, then retry — Required

claude update

Then /plugin update to update the plugin and reopen the session.

2. Run the hook script manually — Required

bash <plugin-dir>/session-start.sh

See the real error (CSDN case path: running session-start.sh manually to locate it).

3. On Windows, switch to the skills-only form — Required

A path that doesn't depend on hooks (see symptom-6 entry): copy skills/ into the skills directory and use it as skills.

How to confirm it works

Startup no longer reports a hook error:

New Claude Code session starts → no SessionStart hook error

Or the manual hook run outputs normally (no errors).

Other environments

Symptom

After install, Claude Code startup reports a hook error (SessionStart hook execution failed).

Cause

Claude Code path-handling bug on Windows (upstream Issue #420 belongs to this scenario); or plugin version mismatch with the Claude Code version.

Solution

1. Upgrade Claude Code and the plugin version, then retry.
2. Run the corresponding hook script manually (session-start.sh) to see the real error.
3. On Windows you can switch to the pure-skills form (does not depend on the hook path, see Symptom 6).