What problem does it solve?
Help developers and maintainers turn a vague need for Claude Code hooks into a validated, working implementation by inspecting repositories, recommending a concrete hook strategy, scaffolding the necessary files, updating settings, and running deterministic validations. The skill reduces uncertainty and manual error when adding guard, notification, linting, or typed-runtime hooks across projects.
Core Features & Use Cases
- Repository inspection: Detects .claude folders, settings.json, registered hooks, available runtimes, package managers, and quality commands to recommend an approach.
- Scaffold & bootstrap: Idempotently creates .claude/hooks/, copies opinionated scaffolds, and writes standalone or typed-runtime hook templates.
- Settings orchestration: Patch settings.json without duplicates and register hooks safely.
- Validation & testing: Deterministic validators and a typed-runtime test harness verify hooks are present and executable.
- Use cases: Add a PreToolUse guard for destructive commands, auto-run linters after edits, create desktop notifications on Stop, or migrate to a typed Bun/TypeScript runtime with vendored sources.
Quick Start
Run the inspection script to assess the repository, choose the recommended strategy, and then scaffold or patch hooks with the provided scripts.