{"version":"2.1.224","anchor":"new-post-commit-review-hook-fires-after-git-commits","canonical_anchor":"new-post-commit-review-hook-fires-after-git-commits","heading":"New post-commit review hook fires after git commits","tier":"notice","area":"Git Integration","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/new-post-commit-review-hook-fires-after-git-commits","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### New post-commit review hook fires after git commits\n\nAfter a git commit completes, Claude is now nudged to review what it just committed.\n\n**What**\n\nStartup 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.\n\n**Details**\n\n- Registered as an internal `PostToolUse` callback hook with a timeout of 1, matching the Bash tool names.\n- Fires only when the command looks like a git commit and the output matches commit-shaped patterns such as `create mode` or `N files changed`.\n- Skipped in one mode check; registration sits in the same non-plugin-only startup branch as the session file-access hooks.\n\n**Evidence**\n\n`registerUltrareviewPostCommitHook`\n\n- Area: Git Integration\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 4\/5"}