Create and manage Claude Code hooks for command validation and workflow automation.
npx skills add https://github.com/caioniehues/dotfiles --skill create-hooks-caioniehues
Please help me install this Agent Skill. Skill: create-hooks Source: https://github.com/caioniehues/dotfiles/tree/main/skills/create-hooks Command: npx skills add https://github.com/caioniehues/dotfiles --skill create-hooks-caioniehues
This Skill provides expert guidance for creating, configuring, and using Claude Code hooks. It helps you automate event-driven workflows, validate commands, add notifications, and understand hook types (PreToolUse, PostToolUse, Stop, SessionStart, UserPromptSubmit, etc.), without touching core Claude code.
Start by creating a basic PreToolUse hook configuration that logs each tool input to a file and validates the command pattern.
High-intent search queries and answers about installing and using this skill.
Hooks automate command validation by intercepting events like PreToolUse and PostToolUse. Create a hook configuration with matcher rules and validation logic to block, log, or transform commands before execution, reducing manual checks and improving safety without modifying core Claude Code.
Claude Code supports PreToolUse, PostToolUse, Stop, SessionStart, and UserPromptSubmit hooks. PreToolUse validates commands before execution, PostToolUse processes results, SessionStart initializes state, UserPromptSubmit filters prompts, and Stop handles cleanup—each serves specific automation and observability needs.
Yes. Hooks let you capture tool inputs, outputs, and session events to log to files or external systems and trigger notifications. Configure listeners on hook events to track execution flow, errors, and decisions, providing full transparency and audit trails for your automated workflows.
Hooks support JSON-based input/output schemas with matcher-based tool filtering. Define schemas in your hook configuration to validate command arguments and structure before execution, ensuring only compliant inputs proceed and blocking invalid requests automatically.
No. Hooks operate independently of Claude Code internals. Configure them as external event listeners that respond to PreToolUse, PostToolUse, and other session events—enabling automation, validation, and safety checks without touching core code.
Implement logging hooks on SessionStart and PreToolUse events to track hook execution and matcher results. Log configuration state, event payloads, and decision outcomes to identify mismatched patterns or validation failures quickly.
gountharCreate, validate, and configure Claude Code hooks with event triggers.
gamingshadow608-starEnforce structured logging, tracing, metrics, and immutable audit trails with OpenTelemetry.
kivo360Configure Claude Code safety hooks across PreToolUse, PostToolUse, SessionStart, Notification, and Stop events.
yu-iskwImplement and validate Claude Code hook configurations and executable scripts.
