How do I share a hook with my team?

Define the hook in your project's .claude/settings.json file and commit it to your git repository to share the automation with your entire team.

What are Claude Code hooks?

Hooks are executable scripts that run in response to specific events during Claude's execution, allowing for real-time validation, automation, and context management.

What is the difference between a hook and a skill?

Hooks are event-driven and run automatically (e.g., after every file write), while skills are discoverable capabilities that Claude chooses to use proactively to solve complex problems.

Can I use hooks to block Claude from performing certain actions?

Yes, by using PreToolUse hooks with specific exit codes (like code 2), you can deny permissions or provide feedback that prevents Claude from executing problematic commands.

Automation Hook Guide

Name: Automation Hook Guide
Author: Mission42-ai

byMission42-ai

Productivity & Workflow

Streamlines Claude Code workflows by guiding the creation of custom execution hooks for validation, automation, and context injection.

About

The Automation Hook Guide is a specialized skill designed to help developers extend Claude Code through event-driven execution hooks. It provides a structured workflow for implementing PreToolUse validation, PostToolUse automation, and session-level context injection. Whether you need to enforce security policies, automatically format code after edits, or ensure tests pass before Claude finishes a task, this skill provides the schemas, best practices, and configuration templates necessary to build robust, project-specific or personal automations.

Key Features

Comprehensive schemas for PreToolUse, PostToolUse, and SessionStart events
Templates for both project-wide (shared) and personal (local) hook configurations
0 GitHub stars
Step-by-step workflow for hook event selection and matcher design
Detailed guidance on exit codes for blocking versus non-blocking validation
Debugging patterns including JSON piping and Claude debug mode instructions

Use Cases

Enforcing linting and formatting rules automatically after Claude modifies source files
Injecting project-specific architectural guidelines into every new Claude session
Creating security guardrails that block or require approval for specific shell commands

About

Key Features

Comprehensive schemas for PreToolUse, PostToolUse, and SessionStart events
Templates for both project-wide (shared) and personal (local) hook configurations
0 GitHub stars
Step-by-step workflow for hook event selection and matcher design
Detailed guidance on exit codes for blocking versus non-blocking validation
Debugging patterns including JSON piping and Claude debug mode instructions

Use Cases

Enforcing linting and formatting rules automatically after Claude modifies source files
Injecting project-specific architectural guidelines into every new Claude session
Creating security guardrails that block or require approval for specific shell commands