Hook Development

Topics in the source

• Hook Development for Claude Code Plugins
• Overview
• Hook Types
• Prompt-Based Hooks (Recommended)
• Command Hooks
• Hook Configuration Formats
• Plugin hooks.json Format
• Settings Format (Direct)

Hooks are event-driven automation scripts that execute in response to Claude Code events. Use hooks to validate operations, enforce policies, add context, and integrate external tools into workflows. Key capabilities: Validate tool calls before execution (PreToolUse) React to tool results (PostToolUse) Enforce completion standards (Stop, SubagentStop) Load project context (SessionStart) Automate workflows across the development lifecycle Use LLM-driven decision making for context-aware validation: Supported events: Stop, SubagentStop, UserPromptSubmit, PreToolUse Benefits: Context-aware decisions based on natural language reasoning Flexible evaluation logic without bash scripting Better edge case handling Easier to maintain and extend Execute bash commands for deterministic checks: Use for: Fast deterministic validations File system operations External tool integrations Performance-critical checks For plugin hooks in hooks/hooks.json, use wrapper format: Key points: description field is optional hooks field is required wrapper containing actual hook events This is the plugin-specific format Example: For user settings in .claude/settings.json, use direct format: Key points: No wrapp

This is an excerpt. Refer to the complete source and its current requirements.