hook-creator

Hooks let you automate Claude Code behavior across lifecycle events like PreToolUse, PostToolUse, and SessionStart. Define event-triggered commands in a JSON configuration file (in ~/.claude/settings.json or .claude/settings.json) that specify which tools or events fire actions, then Claude Code executes them automatically.

Claude Code supports five lifecycle events for hooks: PreToolUse (before tool execution), PostToolUse (after tool execution), Notification (alert events), SessionStart (when a session begins), and SessionEnd (when a session ends). Each event type lets you attach custom command blocks and matchers.

Use PreToolUse hooks with tool matchers to inspect incoming commands. Configure hooks to run logging or validation scripts that read stdin with jq, then return exit code 0 to allow or exit code 2 to block actions. Store hook definitions in project or user settings for persistent protection.

Yes. Hooks can be stored in either user settings (~/.claude/settings.json) for global application or project settings (.claude/settings.json) for local scope. Project-scoped hooks override user settings and let you enforce team-specific automation and permissions.

Hooks support custom permission enforcement through exit codes and pre/post tool command blocks. Define matcher-based conditions that trigger specific actions before or after tools run, enabling automatic formatting, custom workflows, and permission validation without modifying agent code.