What lifecycle events can I trigger hooks on?

You can trigger hooks on SessionStart, SessionEnd, PreToolUse, PostToolUse, UserPromptSubmit, Notification, Stop, and PreCompact events.

Can I use hooks for security and permissions?

Yes, PreToolUse hooks allow you to intercept tool calls and return a permissionDecision of 'allow' or 'deny', providing a layer of custom security for sensitive operations.

How do hooks handle errors or blocked actions?

Hooks use exit codes: 0 for success, 2 for a blocking error that sends feedback to Claude, and other codes for non-blocking errors. Advanced logic can be handled via JSON output.

Where are these hook configurations saved?

Hooks are configured in settings files located at ~/.claude/settings.json for global application or .claude/settings.json for project-specific automation.

Claude Code Lifecycle Hooks

Name: Claude Code Lifecycle Hooks
Author: reggiechan74

byreggiechan74

Productivity & Workflow

Automates validation, data transformation, and custom workflows by hooking into Claude Code's internal lifecycle events.

About

This skill empowers developers to extend Claude Code's functionality by executing automated scripts during specific events, such as tool execution, session startup, or prompt submission. It provides a robust framework for implementing custom security policies, automatic code formatting, and context-aware environment setups, ensuring a more controlled and efficient AI-assisted development workflow through automated bash commands and JSON-based decision logic.

Key Features

Custom permission management and security policy enforcement for CLI commands
Lifecycle event triggers including SessionStart, PreToolUse, and UserPromptSubmit
Pattern-based tool matching with full regex support for granular control
Environment variable persistence across session commands via CLAUDE_ENV_FILE
Automated code formatting and validation post-tool execution
0 GitHub stars

Use Cases

Injecting project-specific context or dynamic environment variables at the start of every session
Blocking the execution of high-risk shell commands or access to sensitive files in production environments
Automatically running Prettier or linters after Claude modifies source files to maintain code standards

About

Key Features

Custom permission management and security policy enforcement for CLI commands
Lifecycle event triggers including SessionStart, PreToolUse, and UserPromptSubmit
Pattern-based tool matching with full regex support for granular control
Environment variable persistence across session commands via CLAUDE_ENV_FILE
Automated code formatting and validation post-tool execution
0 GitHub stars

Use Cases

Injecting project-specific context or dynamic environment variables at the start of every session
Blocking the execution of high-risk shell commands or access to sensitive files in production environments
Automatically running Prettier or linters after Claude modifies source files to maintain code standards