julien-dev-hook-creator

Name: julien-dev-hook-creator
Availability: InStock
Author: theflysurfer

Create Claude Code hooks for lifecycle events with JSON input and exit codes.

Updated Aug 27, 2026

Search Tags:#automation #shell #lifecycle #hook # Claude Code

Ready to run

npx skills add https://github.com/theflysurfer/claude-skills-marketplace --skill julien-dev-hook-creator

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: julien-dev-hook-creator
Source: https://github.com/theflysurfer/claude-skills-marketplace/tree/main/skills/julien-dev-hook-creator
Command: npx skills add https://github.com/theflysurfer/claude-skills-marketplace --skill julien-dev-hook-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill guides the creation of Claude Code hooks—deterministic shell commands or LLM prompts that execute at specific lifecycle events. It enables automation, validation, and logging for Claude Code workflows.

Core Features & Use Cases

Hook lifecycle coverage: SessionStart, SessionEnd, PreToolUse, PostToolUse, etc.
Template-based hooks: provides hook templates to start from
Configuration guidance: describes where to place hooks (project vs global)

Quick Start

Define a new hook in ~/.claude/settings.json or .claude/settings.json with a command block and a timeout.

Frequently Asked Questions about julien-dev-hook-creator

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

FAQPage Schema

How do I automate Claude Code lifecycle events with hooks?▼

Claude Code hooks are deterministic shell commands or prompts executed at specific lifecycle events like SessionStart, SessionEnd, PreToolUse, PostToolUse, and UserPromptSubmit. Define hooks in ~/.claude/settings.json or .claude/settings.json with a command block and timeout to enable validation, logging, environment setup, and external-tool integration.

Where do I configure Claude Code hooks—globally or per project?▼

Hooks can be configured in two locations: ~/.claude/settings.json for global hooks across all Claude Code sessions, or .claude/settings.json in a project directory for project-specific hooks. Both support the same hook template structure and settings.

What exit codes do Claude Code hooks use, and what do they mean?▼

Claude Code hooks use exit code 0 to continue execution and exit code 2 to block or prevent the lifecycle event from proceeding. These deterministic exit codes enable hooks to enforce validation and gating logic across automation workflows.

Can I use Claude Code hooks for validation and logging across multiple sessions?▼

Yes. Hooks run deterministically at defined lifecycle events, supporting validation, logging, and environment setup across both global and project configurations. Input and output are handled as JSON, making hooks compatible with external-tool integration and cross-session automation.

What lifecycle events can Claude Code hooks intercept?▼

Claude Code hooks support SessionStart, SessionEnd, PreToolUse, PostToolUse, and UserPromptSubmit events. Each event enables different automation patterns—SessionStart for environment setup, PreToolUse for validation, PostToolUse for logging, and UserPromptSubmit for prompt-level gating.

Do Claude Code hooks require shell scripting knowledge?▼

Hooks can be defined as either deterministic shell commands or LLM prompts, so you can use shell scripting, structured configuration, or prompt-based logic depending on your automation need. Shell command hooks must return defined exit codes (0 or 2) and handle JSON input/output.