This skill should be used when the user asks to "create a hook", "add a hook", "write a hook", or mentions Claude Code hooks. Also suggest this skill when the user asks to "automatically do X" or "run X before/after Y" as these are good candidates for hooks.
PreToolUse command blocking hook
Settings file location
100%
100%
Script file location
100%
100%
Script is executable
0%
0%
Bash shebang
100%
100%
Pipefail option
100%
100%
Stdin JSON parsing
70%
100%
Exit 2 for blocking
100%
100%
Stderr for block message
0%
100%
Case-sensitive Bash matcher
100%
100%
PreToolUse event
100%
100%
Hook type is command
100%
100%
Exit 0 for allowed commands
100%
100%
Non-blocking error exit
100%
100%
PostToolUse quality enforcement hook
PostToolUse event used
100%
100%
Edit matcher
100%
100%
Settings file location
100%
100%
Script file location
100%
100%
Script is executable
0%
0%
Bash shebang
100%
100%
Pipefail option
100%
100%
File path extraction
80%
100%
No exit 2 blocking
0%
100%
Feedback to stdout
100%
70%
File type filtering
100%
100%
Hook type is command
100%
100%
Non-zero exit does not block
0%
100%
Hook lifecycle and activation workflow
Restart or /hooks required
100%
100%
Snapshot-at-startup explanation
100%
100%
JSON validation command
100%
100%
Debug logging technique
100%
100%
Case-sensitive matcher check
100%
100%
Early exit for non-push commands
100%
100%
Exit 2 blocking with stderr
100%
100%
Settings file location
100%
100%
Script file location
100%
100%
Script executable
40%
0%
Timeout configuration
100%
100%
Stdin JSON parsing with jq
100%
100%
disableAllHooks check
0%
100%
92f335c
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.