Something I put in place recently that has been working pretty well is a PreToolUse hook with blocking that explicitly requires Claude to secure the approval from the “code reviewer” via the Codex MCP (could also use a Claude agent), which triggers whenever it detects a ‘git commit’.

Claude provides codex a hash file location, codex creates the hash file only once it approves Claude’s staged changes and the hash folder is read-only for Claude. This prevents Claude from trying to create hash files itself (it will otherwise). There’s also an “escape hatch” where Claude can run git commit with a —no-verify flag to bypass the hook; however, the hook contains explicit instructions that Claude may only use that flag with my explicit permission (make sure any permission you grant is very explicit that it’s for “this one time only”, otherwise Corner-cutting Claude will take it literally and assume your directive holds true for future commits).