Hooks

Hooks are another feedback mechanism we can use in Claude code.
​
They run arbitrary commands after certain lifecycle events.
​
There’s one hook I lean on heavily “Stop”.
​
It’s called when Claude has finished generating code. Which maps really nicely to my normal workflow where I would run commands like compile, lint, prettier, etc. to check the code is in a good state before continuing.
​
These commands are generally fast to run and when they fail the error is fed back to the LLM and continue to fix those errors until they pass.
​
I don’t run things like tests here though as they take too long to run and it would be a bit annoying adding on an extra minute or so between code generation sessions.
​
There’s a better hook for those “SessionEnd”
​
This works well because it’s when I’m shutting down the session so I don’t mind it taking a bit more time. Plus at this point in my workflow I’m already going to run them to make sure my pull request will past the CI checks.
​
If you want to set these up yourself run /hooks and select the lifecycle event you want to hook into, then follow the steps, some hooks require a matcher to further refine when it should run, others like "stop" don’t.
​
Have you got any good hooks I should consider?