Claude Code hooks are user-defined ... deterministic control over Claude Code’s behavior, ensuring certain actions always happen rather than relying on the LLM to choose to run them. For reference documentation on hooks, see Hooks reference. Example use cases for hooks incl...

Recognizes the same matcher values as PreToolUse. Runs when Claude Code sends notifications. Notifications are sent when: Claude needs your permission to use a tool. Example: “Claude needs your permission to use Bash”

Chat transcript extraction - PostToolUse hook converts JSONL transcripts to readable JSON format · Warning: The chat.json file contains only the most recent Claude Code conversation. It does not preserve conversations from previous sessions - each new conversation is fully copied and overwrites the previous one.

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 in Claude Code are defined in one of your settings files. ~/.claude/settings.json - User settings .claude/settings.json - Project settings .claude/settings.local.json - Local project settings (not committed) Wherever you want to add GitButler to handle your commits automatically, you can add us as a hook by adding the following to the hooks array in whatever settings file you want to use: { "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" } ] } ] } }

Claude Code Hooks Reference · Design Document: docs/design/hooks_implementation.md (available in source repository) Examples: See examples/hooks/ directory in the source repository · Test Suite: See test/claude_agent_sdk/hooks/ directory in the source repository ·

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 - So, here is a very simple tutorial on how you can add a pretty useful hook to your Claude Code workflow in a few minutes as an example of what this can do and how to set it up.

The hook script receives the tool input JSON via stdin and outputs the modified JSON to stdout. Claude Code uses the modified input for tool execution.

July 2, 2025 - Much like Git hooks, you can use Claude Code Hooks to ensure quality before a commit is made. This example runs a custom script to check for API keys or perform other validation steps just before Claude is allowed to use the git_commit tool.

If your hook scripts aren't executing properly, it might be due to relative paths in your .claude/settings.json. Claude Code documentation recommends using absolute paths for command scripts.

October 7, 2025 - Add this content to .claude/hooks/log-implementation.py: #!/usr/bin/env python3 """ Claude Code Implementation Logger Hook Logs every tool execution to a JSONL file """ import json import sys import os from datetime import datetime from pathlib import Path # Get project directory from Claude Code environment variable PROJECT_DIR = os.environ.get('CLAUDE_PROJECT_DIR', os.getcwd()) # Configure where logs are stored LOG_DIR = Path(PROJECT_DIR) / '.claude' / 'logs' LOG_FILE = LOG_DIR / 'implementation-steps.jsonl' def ensure_log_dir(): """Create log directory if it doesn't exist""" LOG_DIR.mkdir(p

July 8, 2025 - Claude Code has introduced hooks that now automate your development workflow in a way similar to using triggers. I have just tested it with my custom script, and it’s mind-blowing how it integrates…

September 12, 2025 - # Code quality check claude -p "Review the latest commit for potential issues" # Automated documentation claude -p "Generate API documentation for all endpoint files" ... # GitHub Actions workflow name: Claude Code Review on: [pull_request] jobs: review: runs-on: ubuntu-latest steps: - uses: actions/checkout@v4 - name: Claude Code Review run: | claude -p "Review this PR for security vulnerabilities and performance issues" \ --output-format json > review-results.json ... #!/bin/bash # .git/hooks/pre-commit changed_files=$(git diff --cached --name-only --diff-filter=ACM) if [ -n "$changed_files" ]; then claude -p "Review these changed files for issues: $changed_files" \ --output-format stream-json fi

The real power comes from editing .claude/hooks/index.ts. You get full TypeScript support with typed payloads: // Example: Track and log specific tool usage async function preToolUse(payload: PreToolUsePayload): Promise<HookResponse> { // Full type safety - TypeScript knows exactly what's in the payload!

2 weeks ago - Pro tip: This is the same file ... For example, you can explicitly allow Claude to read all files in a directory so that you don't have to approve it every time, or block any modification of sensitive files....

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