scaffold-cc-hooks

Audit the target project first, then scaffold Claude Code hooks with a deterministic bash-first layout.

Decision Tree

What is the user asking for?

• New Claude Code hooks in a project with no hook setup yet: Run live docs verification, audit the project, choose a hook plan, then scaffold.
• Existing .claude/settings*.json or .claude/hooks/ files: Audit what already exists, choose additive or overhaul, then regenerate only the managed hook layer.
• Existing hooks that show up in /hooks but never actually fire: Treat workspace trust as the first diagnostic. Check ~/.claude.json for the exact project path before debugging settings or script logic, then offer to enable trust if it is still off.
• Existing hooks plus possible Claude Code feature drift: Verify the live official hook event list before writing files. If the docs changed, update the scaffold inputs first.
• Explanation only, not implementation: Read references/hook-events.md and references/scaffold-layout.md, then answer without scaffolding.