Free client-side tool
Claude Code Hooks Config Generator
Pick lifecycle events and actions, then copy a settings.json hooks block that follows the current Claude Code hook schema.
Key facts
Before you copy the output
- Runs entirely in your browser; no settings data is sent anywhere.
- Uses current event names, matcher groups, and command hook fields from the Claude Code hooks reference.
- Stop and PostToolBatch hooks intentionally omit matchers because those events always fire.
Output
Copy the settings.json hooks block
How to use it
- Choose the lifecycle actions your repository should enforce.
- Set the hook script directory and package-manager command shape.
- Copy the generated JSON into the appropriate Claude Code settings file.
- Create and review the referenced hook scripts before committing shared settings.
Sources checked
Generated output is a starter, not an official policy recommendation. Review commands, paths, and permissions against your own repository before using it.
FAQ
Does this create hook scripts for me?
No. It generates the Claude Code settings.json hooks block and lists the script paths to create. Hook scripts should be small, reviewed, and repository-specific.
Can I use the output in .claude/settings.json?
Yes, if the hook policy is shared by the project. Use .claude/settings.local.json for private local hooks and managed settings for organization-wide policy.