Where should I store my Claude Code hook configurations?

Configurations are stored in .claude/settings.json for project-specific hooks, .claude/settings.local.json for private local hooks, or ~/.claude/settings.json for global settings.

What happens if a hook script takes too long to run?

Hooks have a default timeout of 60 seconds. You can customize this up to 300 seconds in your configuration to prevent runaway scripts from hanging the agent.

What are the main hook events available in Claude Code?

Key events include PreToolUse (triggers before tools run), PostToolUse (after success), UserPromptSubmit (when a user sends a message), and SessionStart/End.

How do I block a dangerous action using a hook?

You can create a PreToolUse hook that inspects the tool input and exits with code 2, providing a JSON object with a 'block' decision to stop the execution.

Can I use environment variables in my hook scripts?

Yes, Claude Code provides variables like CLAUDE_PROJECT_DIR to locate the root directory and CLAUDE_CODE_REMOTE to identify the environment.

Claude Code Hooks Creator

Name: Claude Code Hooks Creator
Author: BrendanShields

byBrendanShields

•

Productivity & Workflow

Automates and customizes Claude Code workflows through event-driven script hooks and configuration.

About

The Creating Hooks skill empowers users to extend Claude Code's capabilities by implementing custom logic triggered by specific lifecycle events. It provides a structured framework for selecting hook events—such as tool execution or session starts—configuring local and project-level settings, and developing robust scripts that can block actions, inject context, or log activity. This skill is essential for developers looking to enforce security policies, automate repetitive tasks, or integrate Claude Code deeper into their specialized development environment using standardized JSON-based communication.

Key Features

Step-by-step guidance for event-driven hook creation (PreToolUse, SessionStart, etc.)
1 GitHub stars
Security-focused script templates with timeout management and path validation
Standardized JSON-based decision logic for blocking or allowing AI actions
Automated configuration management for local and project-level settings.json
Advanced matcher patterns using regex for precise tool targeting

Use Cases

Automatically injecting project-specific documentation or coding standards at the start of every session
Preventing the AI from editing sensitive files like .env or credentials by blocking specific tool paths
Creating custom audit logs for all tool interactions to track AI agent behavior and performance

About

Key Features

Step-by-step guidance for event-driven hook creation (PreToolUse, SessionStart, etc.)
1 GitHub stars
Security-focused script templates with timeout management and path validation
Standardized JSON-based decision logic for blocking or allowing AI actions
Automated configuration management for local and project-level settings.json
Advanced matcher patterns using regex for precise tool targeting

Use Cases

Automatically injecting project-specific documentation or coding standards at the start of every session
Preventing the AI from editing sensitive files like .env or credentials by blocking specific tool paths
Creating custom audit logs for all tool interactions to track AI agent behavior and performance