create-hooks — Claude Code skill: what it does, how to install
The create-hooks skill explains how Claude Code hooks work and gives ready configs for blocking dangerous commands, logging, and auto-formatting.
MIT ★ 1,988 updated 2026-04-01
/plugin marketplace add glittercowboy/taches-cc-resources
/plugin install taches-cc-resources@taches-cc-resourcesWhat create-hooks does
The skill walks through Claude Code's hook events — PreToolUse, PostToolUse, Stop, SessionStart, UserPromptSubmit and others — each of which fires a shell command or an LLM-evaluated prompt tied to a matcher that filters which tools trigger it (say, Bash or mcp__.*). A hook can return {"decision": "block"} to stop an action, rewrite tool input, or just observe and record what Claude does.
Sample configs cover a desktop alert via osascript, blocking git push --force and rm -rf through a prompt-type hook, running prettier on files after Write or Edit, and injecting sprint context at SessionStart. Configuration lives in .claude/hooks.json for a project or ~/.claude/hooks.json for a user, and claude --debug shows which hooks actually matched.
Choosing between hook types matters: a command hook runs a fixed script and answers fast, while a prompt hook hands the decision to the LLM and suits judgment calls that plain pattern matching can't make.
What it helps with
- stop destructive bash commands before they run
- auto-format files with prettier right after an edit
- log every Bash invocation to a file
- inject current sprint context at session start
- fire a desktop notification when Claude is waiting on input
Example prompts for the agent
- Write a hook that blocks
git push --forceandrm -rfin Bash - Set up a PostToolUse hook that runs prettier after Write and Edit
- Add a SessionStart hook that injects the current sprint into context
How to install create-hooks
1Plugin marketplace
/plugin marketplace add glittercowboy/taches-cc-resources/plugin install taches-cc-resources@taches-cc-resourcesThis installs the whole taches-cc-resources plugin with all its skills
2Skills CLI (Vercel)
npx skills add glittercowboy/taches-cc-resources --skill create-hooks -a claude-code3Manually: put the files in place
~/.claude/skills/create-hooks/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/create-hooks/
1Skills CLI (Vercel)
npx skills add glittercowboy/taches-cc-resources --skill create-hooks -a codex2Manually: put the files in place
.agents/skills/create-hooks/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add glittercowboy/taches-cc-resources --skill create-hooks -a cursor2Manually: put the files in place
.cursor/skills/create-hooks/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install glittercowboy/taches-cc-resources skills/create-hooks2Manually: put the files in place
.github/skills/create-hooks/SKILL.md1Skills CLI (Vercel)
npx skills add glittercowboy/taches-cc-resources --skill create-hooks -a gemini-cli2Platform CLI
gemini skills install https://github.com/glittercowboy/taches-cc-resources --path skills/create-hooksManually: put the files in place
.devin/skills/create-hooks/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about create-hooks
How do I install create-hooks in Claude Code?
Through the marketplace: run /plugin marketplace add glittercowboy/taches-cc-resources, then /plugin install taches-cc-resources@taches-cc-resources.
What does create-hooks do?
It teaches how to configure Claude Code hooks — events, matchers, and shell or prompt-based actions that validate tool calls, log activity, or automate workflows.
What's the difference between command and prompt hook types?
A command hook runs a shell script and suits simple checks or logging, while a prompt hook sends an LLM a prompt with $ARGUMENTS and expects back a JSON decision, which fits cases that need reasoning rather than fixed rules.
Source text
SKILL.md · MIT
---
name: create-hooks
description: Expert guidance for creating, configuring, and using Claude Code hooks. Use when working with hooks, setting up event listeners, validating commands, automating workflows, adding notifications, or understanding hook types (PreToolUse, PostToolUse, Stop, SessionStart, UserPromptSubmit, etc).
---
<objective>
Hooks are event-driven automation for Claude Code that execute shell commands or LLM prompts in response to tool usage, session events, and user interactions. This skill teaches you how to create, configure, and debug hooks for validating commands, automating workflows, injecting context, and implementing custom completion criteria.
Hooks provide programmatic control over Claude's behavior without modifying core code, enabling project-specific automation, safety checks, and workflow customization.
</objective>
<context>
Hooks are shell commands or LLM-evaluated prompts that execute in response to Claude Code events. They operate within an event hierarchy: events (PreToolUse, PostToolUse, Stop, etc.) trigger matchers (tool patterns) which fire hooks (commands or prompts). Hooks can block actions, modify tool inputs, inject context, or simply observe and log Claude's operations.
</context>
<quick_start>
<workflow>
1. Create hooks config file:
- Project: `.claude/hooks.json`
- User: `~/.claude/hooks.json`
2. Choose hook event (when it fires)
3. Choose hook type (command or prompt)
4. Configure matcher (which tools trigger it)
5. Test with `claude --debug`
</workflow>
<example>
**Log all bash commands**:
`.claude/hooks.json`:
```json
{
"hooks": {
"PreToolUse": [
{
"matcher": "Bash",
"hooks": [
{
"type": "command",
"command": "jq -r '\"\\(.tool_input.command) - \\(.tool_input.description // \\\"No description\\\")\"' >> ~/.claude/bash-log.txt"
}
]
}
]
}
}
```
This hook:
- Fires before (`PreToolUse`) every `Bash` tool use
- Executes a `command` (not an LLM prompt)
- Logs command + description to a file
</example>
</quick_start>
<hook_types>
| Event | When it fires | Can block? |
|-------|---------------|------------|
| **PreToolUse** | Before tool execution | Yes |
| **PostToolUse** | After tool execution | No |
| **UserPromptSubmit** | User submits a prompt | Yes |
| **Stop** | Claude attempts to stop | Yes |
| **SubagentStop** | Subagent attempts to stop | Yes |
| **SessionStart** | Session begins | No |
| **SessionEnd** | Session ends | No |
| **PreCompact** | Before context compaction | Yes |
| **Notification** | Claude needs input | No |
Blocking hooks can return `"decision": "block"` to prevent the action. See [references/hook-types.md](references/hook-types.md) for detailed use cases.
</hook_types>
<hook_anatomy>
<hook_type name="command">
**Type**: Executes a shell command
**Use when**:
- Simple validation (check file exists)
- Logging (append to file)
- External tools (formatters, linters)
- Desktop notifications
**Input**: JSON via stdin
**Output**: JSON via stdout (optional)
```json
{
"type": "command",
"command": "/path/to/script.sh",
"timeout": 30000
}
```
</hook_type>
<hook_type name="prompt">
**Type**: LLM evaluates a prompt
**Use when**:
- Complex decision logic
- Natural language validation
- Context-aware checks
- Reasoning required
**Input**: Prompt with `$ARGUMENTS` placeholder
**Output**: JSON with `decision` and `reason`
```json
{
"type": "prompt",
"prompt": "Evaluate if this command is safe: $ARGUMENTS\n\nReturn JSON: {\"decision\": \"approve\" or \"block\", \"reason\": \"explanation\"}"
}
```
</hook_type>
</hook_anatomy>
<matchers>
Matchers filter which tools trigger the hook:
```json
{
"matcher": "Bash", // Exact match
"matcher": "Write|Edit", // Multiple tools (regex OR)
"matcher": "mcp__.*", // All MCP tools
"matcher": "mcp__memory__.*" // Specific MCP server
}
```
**No matcher**: Hook fires for all tools
```json
{
"hooks": {
"UserPromptSubmit": [
{
"hooks": [...] // No matcher - fires on every user prompt
}
]
}
}
```
</matchers>
<input_output>
Hooks receive JSON via stdin with session info, current directory, and event-specific data. Blocking hooks can return JSON to approve/block actions or modify inputs.
**Example output** (blocking hooks):
```json
{
"decision": "approve" | "block",
"reason": "Why this decision was made"
}
```
See [references/input-output-schemas.md](references/input-output-schemas.md) for complete schemas for each hook type.
</input_output>
<environment_variables>
Available in hook commands:
| Variable | Value |
|----------|-------|
| `$CLAUDE_PROJECT_DIR` | Project root directory |
| `${CLAUDE_PLUGIN_ROOT}` | Plugin directory (plugin hooks only) |
| `$ARGUMENTS` | Hook input JSON (prompt hooks only) |
**Example**:
```json
{
"command": "$CLAUDE_PROJECT_DIR/.claude/hooks/validate.sh"
}
```
</environment_variables>
<common_patterns>
**Desktop notification when input needed**:
```json
{
"hooks": {
"Notification": [
{
"hooks": [
{
"type": "command",
"command": "osascript -e 'display notification \"Claude needs input\" with title \"Claude Code\"'"
}
]
}
]
}
}
```
**Block destructive git commands**:
```json
{
"hooks": {
"PreToolUse": [
{
"matcher": "Bash",
"hooks": [
{
"type": "prompt",
"prompt": "Check if this command is destructive: $ARGUMENTS\n\nBlock if it contains: 'git push --force', 'rm -rf', 'git reset --hard'\n\nReturn: {\"decision\": \"approve\" or \"block\", \"reason\": \"explanation\"}"
}
]
}
]
}
}
```
**Auto-format code after edits**:
```json
{
"hooks": {
"PostToolUse": [
{
"matcher": "Write|Edit",
"hooks": [
{
"type": "command",
"command": "prettier --write $CLAUDE_PROJECT_DIR",
"timeout": 10000
}
]
}
]
}
}
```
**Add context at session start**:
```json
{
"hooks": {
"SessionStart": [
{
"hooks": [
{
"type": "command",
"command": "echo '{\"hookSpecificOutput\": {\"hookEventName\": \"SessionStart\", \"additionalContext\": \"Current sprint: Sprint 23. Focus: User authentication\"}}'"
}
]
}
]
}
}
```
</common_patterns>
<debugging>
Always test hooks with the debug flag:
```bash
claude --debug
```
This shows which hooks matched, command execution, and output. See [references/troubleshooting.md](references/troubleshooting.md) for common issues and solutions.
</debugging>
<reference_guides>
**Hook types and events**: [references/hook-types.md](references/hook-types.md)
- Complete list of hook events
- When each event fires
- Input/output schemas for each
- Blocking vs non-blocking hooks
**Command vs Prompt hooks**: [references/command-vs-prompt.md](references/command-vs-prompt.md)
- Decision tree: which type to use
- Command hook patterns and examples
- Prompt hook patterns and examples
- Performance considerations
**Matchers and patterns**: [references/matchers.md](references/matchers.md)
- Regex patterns for tool matching
- MCP tool matching patterns
- Multiple tool matching
- Debugging matcher issues
**Input/Output schemas**: [references/input-output-schemas.md](references/input-output-schemas.md)
- Complete schema for each hook type
- Field descriptions and types
- Hook-specific output fields
- Example JSON for each event
**Working examples**: [references/examples.md](references/examples.md)
- Desktop notifications
- Command validation
- Auto-formatting workflows
- Logging and audit trails
- Stop logic patterns
- Session context injection
**Troubleshooting**: [references/troubleshooting.md](references/troubleshooting.md)
- Hooks not triggering
- Command execution failures
- Prompt hook issues
- Permission problems
- Timeout handling
- Debug workflow
</reference_guides>
<security_checklist>
**Critical safety requirements**:
- **Infinite loop prevention**: Check `stop_hook_active` flag in Stop hooks to prevent recursive triggering
- **Timeout configuration**: Set reasonable timeouts (default: 60s) to prevent hanging
- **Permission validation**: Ensure hook scripts have executable permissions (`chmod +x`)
- **Path safety**: Use absolute paths with `$CLAUDE_PROJECT_DIR` to avoid path injection
- **JSON validation**: Validate hook config with `jq` before use to catch syntax errors
- **Selective blocking**: Be conservative with blocking hooks to avoid workflow disruption
**Testing protocol**:
```bash
# Always test with debug flag first
claude --debug
# Validate JSON config
jq . .claude/hooks.json
```
</security_checklist>
<success_criteria>
A working hook configuration has:
- Valid JSON in `.claude/hooks.json` (validated with `jq`)
- Appropriate hook event selected for the use case
- Correct matcher pattern that matches target tools
- Command or prompt that executes without errors
- Proper output schema (decision/reason for blocking hooks)
- Tested with `--debug` flag showing expected behavior
- No infinite loops in Stop hooks (checks `stop_hook_active` flag)
- Reasonable timeout set (especially for external commands)
- Executable permissions on script files if using file paths
</success_criteria>
© Lex Christopherson · MIT · glittercowboy/taches-cc-resources