From aidd-context
Generates hooks that run automatically at lifecycle events across AI tools in a project. Use when creating, scaffolding, or refactoring hooks to automate actions at lifecycle points.
How this skill is triggered — by the user, by Claude, or both
Slash command
/aidd-context:08-hook-generateThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Builds one hook: an entry merged into the chosen scope for each supported tool, plus the backing script.
Builds one hook: an entry merged into the chosen scope for each supported tool, plus the backing script.
| # | Action | Role | Input |
|---|---|---|---|
| 01 | capture-hook | Clarify the moment, action, matcher, scope, tools | user request |
| 02 | write-hook | Merge the entry per tool, write the script | the captured spec |
| 03 | validate | Check the file, the merge, and the moment fit | files written |
Run the actions in order, 01 → 03, and run each action's ## Test before the next.
references/hook-authoring.md: the contract (R1-R7), the lifecycle moments, and the handler, matcher, and exit-code model.references/tool-paths.md: per-tool support, moment-to-event names, file formats, scopes, and write targets.assets/hook-template.json: the entry scaffold.assets/hook-script-template.sh: the backing-script scaffold.npx claudepluginhub ai-driven-dev/frameworkDefines, edits, and manages event-driven hooks that activate agents on project events. Tool-agnostic — adapters translate hook definitions into tool-native configurations during sync.
Creates, validates, and refines Claude Code plugin hooks for workflow automation. Supports command hooks (shell scripts), prompt hooks (LLM decisions), event matching, decision schemas, and production safety validation.
Scaffolds Claude Code hooks with templates, validation, and conflict analysis. Analyzes existing hooks, prevents conflicts, and generates boilerplate code automatically.