claude-hook-builder

Claude Code hooks automate validation and approval workflows by triggering on events like PreToolUse and PostToolUse. Define a hook with a trigger event, tool matcher, and bash command or prompt-based logic, then save it to settings.json to automatically validate and approve safe operations without manual intervention.

Supported hook events include PreToolUse, PostToolUse, UserPromptSubmit, Stop, SubagentStop, SessionStart, and SessionEnd. Each event fires at a specific workflow stage, letting you validate inputs, modify prompts, make permission decisions, or trigger automation at the right moment in your Claude Code session.

Yes, Claude Code hooks support both bash command hooks and prompt-based hooks. Bash command hooks execute deterministic validation logic; prompt-based hooks use Claude to make contextual decisions. Choose based on whether you need fast, rule-based automation or intelligent reasoning over tool inputs and outputs.

Define your hook with JSON-based specifications including event type, tool matching rules, and command or prompt logic, then save it to settings.json. The hook builder supports per-scope settings persistence and optional environment variable persistence, so your configuration survives across sessions and applies automatically.

No external dependencies are required. The hook builder works with Claude Code's built-in hook system. You only need to describe your automation scenario—trigger event, target tools, and validation logic—and the builder guides you through JSON definition and settings.json integration.

Validation hooks check tool inputs or outputs and make permission decisions, blocking unsafe operations before they run. Automation hooks trigger actions—like modifying prompts, logging data, or executing setup commands—to streamline repetitive workflows without requiring explicit user approval each time.