scaffold-devin-hooks

Audit the target project first, then scaffold Devin CLI hooks with a deterministic .devin/hooks.v1.json managed layer.

Decision Tree

What is the user asking for?

• New Devin CLI hooks in a project with no hook setup: Verify the live official Devin docs, audit the project, choose a hook plan, then scaffold .devin/hooks.v1.json.
• Existing .devin/hooks.v1.json, .devin/config*.json, or .devin/hooks/ files: Audit what already exists, choose additive or overhaul, then regenerate only the managed hook layer.
• A hook must deny or block agent behavior: Use command hooks that intentionally return exit code 2; read references/hook-events.md before deciding where the block belongs.
• Existing Claude hook config is present: Treat it as an inherited-config risk to inspect, not as the target. Do not write generated Devin hooks to Claude config paths.
• Explanation only, not implementation: Read references/hook-events.md and references/scaffold-layout.md, then answer without editing files.