What problem does it solve? Building event-driven automation for Claude Code requires understanding hook events, JSON configuration formats, input/output schemas, and security practices, which is error-prone without structured guidance and validation tooling. ## 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 hook patterns. - 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 Documentation: Provides proven hook patterns, migration guidance from command to prompt hooks, and advanced techniques like caching, rate limiting, and cross-event workflows. - 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 with sample input before restarting Claude Code. ## Quick Start Create a PreToolUse prompt-based hook in my plugin's hooks.json that validates file writes for path traversal and sensitive files.
