hook-development

This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDEPLUGINROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced

Hook Development for Claude Code Plugins Overview 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 Hook Types Prompt-Based Hooks (Recommended) Use LLM-driven decision making for context-aware validation: json { "type": "prompt", "prompt": "Evaluate if this tool use is appropriate: $TOOLINPUT", "timeout": 30 } Supported events: Stop, SubagentStop, UserPromptSubmit, PreToolUse Benefits: - Context-aware decisions based on natural language reasoning - Flexible evaluation logic without bash script…