After a git commit completes, Claude is now nudged to review what it just committed.
What's wrong with this entry?
Startup registers an internal hook that watches Bash tool output and injects a system message when it sees a completed git commit, so the model is prompted to review what was just committed.
- Registered as an internal
PostToolUsecallback hook with a timeout of 1, matching the Bash tool names. - Fires only when the command looks like a git commit and the output matches commit-shaped patterns such as
create modeorN files changed. - Skipped in one mode check; registration sits in the same non-plugin-only startup branch as the session file-access hooks.
registerUltrareviewPostCommitHook
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Stale editor bridge connections are dropped instead of read
Both mention integration
-
v2.1.234
Git remote URLs can no longer smuggle a different host
Both mention integration
-
v2.1.236
Change detection ignores custom diff drivers and submodules
Both mention integration