hook-developer

Build Claude Code hooks with schemas, registration, and testing patterns.

1|Updated Jan 2, 2026
One-click install
npx skills add https://github.com/tfunk1030/vibe --skill hook-developer-tfunk1030
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hook-developer
Source: https://github.com/tfunk1030/vibe/tree/main/.claude/skills/hook-developer
Command: npx skills add https://github.com/tfunk1030/vibe --skill hook-developer-tfunk1030

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This entry provides a definitive reference for building Claude Code hooks, including input/output schemas, registration patterns, and testing examples, reducing ambiguity for developers.

Core Features & Use Cases

  • Input/Output Schemas: Clear definitions for hook data structures and event payloads to ensure consistent integration with Claude.
  • Registration & Lifecycle: Guidelines for registering hooks in settings.json and implementing events such as PreToolUse, PostToolUse, UserPromptSubmit, and SessionStart.
  • Testing Patterns: Practical testing patterns, examples, and debugging tips to accelerate reliable hook development across common use cases.

Quick Start

Follow these steps to write and test Claude Code hooks using the provided schemas and registration approach.

Frequently Asked Questions about hook-developer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I register Claude Code hooks in settings.json?

You register Claude Code hooks by defining them within settings.json using the correct input and output schemas. This ensures consistent integration with the Claude environment across common use cases.

What is the lifecycle of a Claude Code hook?

The Claude Code hook lifecycle includes events such as PreToolUse, PostToolUse, UserPromptSubmit, and SessionStart. These events define the specific execution stages for hook logic and tool interaction.

How do I test Claude Code hooks for correct schemas and behavior?

You test Claude Code hooks by applying practical testing patterns and debugging tips. This provides a reproducible workflow to validate input/output schemas and behavior across common use cases.

What are the input and output schemas for Claude Code hook event payloads?

Input and output schemas for Claude Code hooks are clear definitions for data structures and event payloads. They ensure consistent integration with the Claude system during tool interaction.

Can I use PreToolUse and PostToolUse hooks to control tool interaction in Claude?

Yes, you can use PreToolUse and PostToolUse hooks to control tool interaction. Implementing these events in settings.json allows you to manage the full hook lifecycle and validate behavior.

Why do I need a reference for building Claude Code hooks?

You need a reference for building Claude Code hooks to reduce ambiguity for developers. It provides definitive schemas, registration patterns, and testing examples for reliable development.