What is the recommended lifecycle for developing a new hook?

The skill recommends a three-phase approach: Phase 1 (Observe) for non-blocking logging, Phase 2 (Automate) for fast background tasks, and Phase 3 (Enforce) for blocking critical errors once patterns are established.

How can I control the order in which multiple hooks run?

Multiple hooks for the same event run in alphabetical order. Use numeric prefixes in filenames (e.g., 01-log.sh, 10-format.sh) to explicitly define the execution sequence.

How do I ensure my hooks don't slow down Claude Code?

Hooks should be designed to execute in under 2 seconds. For longer operations like full test suites, the skill provides patterns for triggering background jobs that don't block the main workflow.

What events can trigger a Claude Code hook?

Hooks can be triggered by various events including UserPromptSubmit, Stop, PreToolUse, PostToolUse, ToolError, SessionStart, and SessionEnd.

Claude Code Hooks Architect

Name: Claude Code Hooks Architect
Author: withzombies

bywithzombies

•

Developer Tools

Implements a systematic approach to building, testing, and scaling Claude Code hooks through progressive observation and automation.

About

The Building Hooks skill provides a comprehensive framework for extending Claude Code's native capabilities through custom lifecycle events. It guides users through a three-phase development strategy—starting with non-blocking observation, moving to background automation, and finally implementing blocking enforcement only when patterns are clear. By providing standardized patterns for build checks, auto-formatting, and context injection, this skill ensures that custom automations remain fast, reliable, and non-disruptive to the developer workflow.

Key Features

Detailed testing and debugging protocols for hook isolation
Progressive enhancement framework (Observe, Automate, Enforce)
Hook composition strategies using numeric execution ordering
13 GitHub stars
Standardized patterns for builds, formatting, and quality reminders
Event-driven automation for the entire Claude Code lifecycle

Use Cases

Injecting project-specific context and skill activation reminders into prompts
Enforcing consistent code styles through auto-formatting stop hooks
Automating TypeScript build checks and error reporting after file edits

About

Key Features

Detailed testing and debugging protocols for hook isolation
Progressive enhancement framework (Observe, Automate, Enforce)
Hook composition strategies using numeric execution ordering
13 GitHub stars
Standardized patterns for builds, formatting, and quality reminders
Event-driven automation for the entire Claude Code lifecycle

Use Cases

Injecting project-specific context and skill activation reminders into prompts
Enforcing consistent code styles through auto-formatting stop hooks
Automating TypeScript build checks and error reporting after file edits