debug-hooks

Claude Code hooks fail to fire when they're not registered in settings.json, the hook files don't exist, or the session environment isn't loading them. Debug hooks by checking project and global settings.json for registration, verifying hook wrapper and bundle files are present, and inspecting project cache outputs for silent failures.

Verify PostToolUse hook registration in settings.json, confirm the hook file exists in your project, manually test the hook using provided Bash commands, and check debug logs for errors. Rebuild your TypeScript after edits and restart your session to apply changes.

Inspect project cache and outputs before editing. Verify hook registration in settings.json, ensure hook files exist, then manually test the hook with reproduction commands. Check for silent failures and rebuild TypeScript after making fixes.

Yes. The debugging workflow applies to both local projects and CI environments. Follow the same steps: verify hook registration in settings.json, check hook file presence, inspect outputs and debug logs, manually test with provided commands, and rebuild after edits.

After editing hook files, rebuild using the TypeScript build process in your environment, then restart your Claude Code session. Verify the changes by manually testing the hook with provided commands and inspecting outputs for errors.

Hook registration in settings.json tells Claude Code which hooks to load and when to trigger them. Check both project-level and global settings.json to ensure your hook is registered; missing registration is a common cause of hooks not firing at SessionStart, PreToolUse, or PostToolUse events.