claude-code-hooks
Provide ready-to-use Claude Code hooks for safety, cost and session feedback.
Browse category →Workflow problem
Find practical Claude Code hook examples
Hook events are useful for repeatable checks, notifications and guardrails, but event names and payloads must match Claude Code’s current hook contract.
The problem
Hook events are useful for repeatable checks, notifications and guardrails, but event names and payloads must match Claude Code’s current hook contract.
Native approach
Define hooks in Claude Code settings and start with a small `PostToolUse` or `PreToolUse` example from the official hooks guide. Test it against a disposable action before relying on it.
Official Claude Code documentation ↗Tools to consider
Review hook scripts before installation because they execute commands in your local environment.
tdd-guard
Block implementation steps until the expected test-first workflow is followed.
Browse category →cc-safety-net
Intercept risky file and Git commands before a coding agent executes them.
Browse category →FAQ
When should I use a hook?
Use one when the action must run on a specific lifecycle event.
Can a skill enforce the same guardrail?
A skill supplies instructions; a blocking hook can enforce a check at tool use.