This page provides reference documentation for implementing hooks in Claude Code.

This page provides reference documentation for implementing hooks in Claude Code.

July 1, 2025 - How do you enable this? I had a look here but couldn’t find it (unless I missed it) https://docs.anthropic.com/en/docs/claude-code/settings ... I changed my whole workflow to spec-driven using UserPromptSubmit Event and Stop hooks.

{ "hooks": { "PreToolUse": [ { "matcher": "Edit|MultiEdit|Write", "hooks": [ { "type": "command", "command": "but claude pre-tool" } ] } ], "PostToolUse": [ { "matcher": "Edit|MultiEdit|Write", "hooks": [ { "type": "command", "command": "but claude post-tool" } ] } ], "Stop": [ { "matcher": "", "hooks": [ { "type": "command", "command": "but claude stop" } ] } ] } } Essentially, you want to run the but claude pre-tool command before any code generation or editing, and the but claude post-tool command after it.

Hooks communicate status and control flow through exit codes: ... Hook executed successfully. stdout shown to user in transcript mode (Ctrl-R) ... Critical: stderr is fed back to Claude automatically.

Claude Code Hooks are callback functions that execute at specific lifecycle events during Claude's agent loop.

Master Claude Code hooks for automated workflow responses. Learn PreToolUse, PostToolUse triggers, smart dispatching patterns, and deployment validation.

Explore our complete guide to hooks in Claude Code. Learn what they are, how they work, and their limitations for true business workflow automation.

July 2, 2025 - This article serves as a comprehensive guide to understanding, configuring, and leveraging Claude Code Hooks to create a fully automated and streamlined development workflow. At their core, Claude Code Hooks are user-defined shell commands that execute automatically at specific points in Claude Code’s lifecycle.

July 8, 2025 - Claude Code has introduced hooks that now automate your workflow in a way similar to triggers — executing automatically at specific points

2 weeks ago - Hooks are configured in your settings files using a JSON structure with event names, matchers (to filter which tools trigger the hook), and the commands to run. They execute in your local environment with your user permissions, receiving information about the triggering event via stdin and communicating back through exit codes and stdout.

%{ hooks: %{ stop: [:compile, :format], subagent_stop: [:compile, :format], post_tool_use: [:compile, :format], # These only run on git commit commands pre_tool_use: [:compile, :format, :unused_deps] } } ... The default blocking?: false setting keeps you informed about issues without causing ...

Numerous specialized agents, slash-commands, and strong documentation. All parts of Claude Code's system prompt, including builtin tool descriptions, sub agent prompts (Plan/Explore/Task), utility prompts (CLAUDE.md, compact, Bash cmd, security review, agent creation, etc.). Updated for each Claude Code version. Professional development environment for Claude Code with spec-driven workflow, TDD enforcement, cross-session memory, semantic search, quality hooks, and modular rules integration.

July 24, 2025 - Since we want to know when something is completed, we'll use the Stop hook, which fires when everything in a session is done. ... .claude/settings.json - Project settings, only runs on that project and should be committed (for the rest of your team) .claude/settings.local.json - Local project settings, meant to not be committed, just for you. Claude Code should look for all of these files, and fire every hook that matches in any of them.

October 7, 2025 - What are Claude Code Hooks? Claude Code hooks are automated scripts that run at specific points in Claude Code’s lifecycle. They allow you to: Hook...

September 29, 2025 - It adds some hooks for what code should run before edits are accepted, such as run Prettier on a specific file, or after edits, like write a type check on a specific file to make sure that it only accepts good and correct files.