What is the difference between prompt-based and command hooks?

Prompt-based hooks use LLM reasoning to perform context-aware evaluations using natural language, while command hooks execute deterministic bash scripts for performance-critical or file-system tasks.

Where should plugin-specific hooks be configured?

Plugin-specific hooks should be defined in a 'hooks/hooks.json' file within your plugin directory using the required wrapper format containing the 'hooks' field.

How do I persist environment variables in Claude Code?

You can use a SessionStart hook to append export commands to the file specified by the $CLAUDE_ENV_FILE environment variable, which persists them for the duration of the session.

Can I run multiple hooks for the same event?

Yes, Claude Code executes all matching hooks in parallel. This allows you to separate concerns, such as having one hook for security validation and another for logging.

Claude Code Hook Development

Name: Claude Code Hook Development
Author: EricGrill

byEricGrill

•

Developer Tools

Provides comprehensive implementation patterns and best practices for creating event-driven automation hooks within Claude Code plugins.

The Hook Development skill is an essential resource for developers looking to extend Claude Code's capabilities through sophisticated automation. It offers detailed guidance on implementing both prompt-based and command-driven hooks, allowing for context-aware validation, security enforcement, and workflow automation. By mastering events like PreToolUse, SessionStart, and Stop, developers can create plugins that proactively block dangerous commands, automatically load project context, and verify task completion against specific standards, resulting in safer and more efficient AI-driven development environments.

Key Features

01Standards for secure input validation and path traversal prevention

02Detailed implementation patterns for PreToolUse, PostToolUse, and SessionStart events

03Best practices for optimizing parallel hook execution and performance

04Comprehensive guidance for prompt-based and command-based hook architectures

05Instructions for persisting environment variables via session-level automation

0611 GitHub stars

Use Cases

01Automating project setup by loading environment-specific context at the start of a session

02Enforcing security policies by validating file writes and bash commands before execution

03Implementing automated quality gates that verify code changes before Claude completes a task

Key Features

01Standards for secure input validation and path traversal prevention

02Detailed implementation patterns for PreToolUse, PostToolUse, and SessionStart events

03Best practices for optimizing parallel hook execution and performance

04Comprehensive guidance for prompt-based and command-based hook architectures

05Instructions for persisting environment variables via session-level automation

0611 GitHub stars

Use Cases

01Automating project setup by loading environment-specific context at the start of a session

02Enforcing security policies by validating file writes and bash commands before execution

03Implementing automated quality gates that verify code changes before Claude completes a task