hook-factory_skill

Overview

This skill generates production-ready Claude Code hooks with interactive Q&A, automated installers, and strong validation. It provides three generation modes (interactive, natural language, template) and 10 production templates covering 7 event types. The outputs include validated hook.json and README.md plus optional automated installation for macOS/Linux.

How this skill works

The tool inspects your request (interactive prompts, plain English, or explicit template) then selects a template and substitutes variables. It runs a 4-layer validation (structure, safety, matcher, event-specific) plus secrets and command checks, writes the generated hook folder, and can auto-install using a Python or Bash installer with backups and rollback. All generated hooks include tool detection, silent-failure safeguards, and timeout settings tuned to the event.

When to use it

• Auto-format code after editing
• Auto-stage files with git on edits
• Run tests when an agent or subagent finishes
• Load project context at session start
• Pre-validate tools or commands before execution
• Create custom workflow automations for Unix environments

Best practices

• Start with Interactive Mode for guided defaults and safety checks
• Review generated README.md and hook.json before installing
• Test new hooks in a safe project or branch first
• Use template mode for precise control and advanced customization
• Enable auto-install only after verifying the generated commands locally
• Monitor ~/.claude/logs/ for runtime troubleshooting

Example use cases

• Auto-format Python files after editing using post_tool_use_format with black
• Automatically git-add changed files via post_tool_use_git_add
• Run pytest or jest when an agent stops using subagent_stop_test_runner
• Load TODO.md or project context on session start via session_start_load_context
• Run semgrep or bandit security scans before push with security_scan_code