hook-creator

Hooks are event-driven configurations that run at Claude Code lifecycle events like PreToolUse and PostToolUse. Create a JSON hook configuration in your project's .claude/settings.json or user ~/.claude/settings.json to automate formatting, logging, and policy enforcement across tool execution.

Claude Code supports PreToolUse (before tool execution), PostToolUse (after tool execution), and Notification events. Each event type lets you define matcher patterns to target specific tools or apply actions globally, with full control over execution context and exit code semantics.

Yes. Hooks support file protection and custom permission enforcement as part of their governance capabilities. Define matchers and commands in your hook configuration to apply policies at PreToolUse or PostToolUse events across user, project, or session contexts.

Store hook configurations as JSON in either your user settings (~/.claude/settings.json) for personal use or in project settings (.claude/settings.json) for team-wide policies. Choose based on whether you want hooks to apply globally or to a specific project.

Define your hook configuration in JSON with event type, matcher patterns, and command logic, then place it in your chosen storage location. Test by triggering the matching event—Claude Code parses stdin JSON input with jq and executes your hook command, allowing you to verify formatting, logging, or policy enforcement before rollout.

Hooks operate across user, project, and session contexts. This lets you set global policies at the user level, override them per project, and apply temporary hooks for specific sessions—giving you fine-grained control over when and where automation and governance run.