What problem does it solve? Building hooks for Claude Code plugins requires understanding event types, JSON configuration formats, input/output schemas, and security practices, and mistakes cause silent failures or broken workflows. ## Core Features & Use Cases - Hook Implementation Guidance: Covers all hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification) with both prompt-based and command-based configurations. - Validation and Testing Scripts: Includes validate-hook-schema.sh for hooks.json structure checks, test-hook.sh for running hooks against sample input, and hook-linter.sh for best-practice enforcement. - Reference Patterns and Examples: Provides proven hook patterns, migration guidance from command to prompt hooks, and working example scripts for write validation, bash validation, and context loading. - Use Case: When adding a PreToolUse hook to block dangerous bash commands in a plugin, use this Skill to write the hooks.json entry, validate it with the schema script, and test it before restarting Claude Code. ## Quick Start Create a PreToolUse hook that validates file writes and blocks path traversal in my Claude Code plugin.
