Grip

grip

A git hook that won't let you push code you can't explain.

Before your code leaves your machine, grip reads the diff and asks you about it: why it is
built this way, where it fails, what a malicious caller could do, how you know it works.
In the terminal, or on a whiteboard of your change in the browser. A model grades your
answers out of 100. Below your team's pass mark, the push waits.

It checks the developer, not the code. Let AI write it; just be able to defend it.
Follow one real change from commit to push
to see what it asks and how it grades.
"If I ask 'why did you do X instead of Y?', 'what happens if this actor behaves
maliciously?' [...] you should be able to answer confidently."
Mitchell Hashimoto, on X, about
the whiteboard defense (not affiliated with grip)

Try it in 30 seconds

No hook, no account, no API key: the fake provider runs the whole flow offline.

The offline grader does not read your answers, it only checks their length: twenty
characters, or the word "because", gets full marks. Any long answer passes and a row of
"idk" fails, so this shows the flow, not the grading. For questions written from your diff
and real grading, use a model you have (--provider claude-code, codex, gemini or
anthropic), or read the walkthrough.

Nothing is blocked until you install the hook with grip init.

Features

- Five questions from your diff, graded against a hidden rubric into a Grip Score out
  of 100. Never line numbers or trivia.
- grip whiteboard: your change drawn as parts and arrows in the browser, with the
  questions pinned to it, including what a malicious actor could do. Set
  hook_mode = "whiteboard" and every push is defended there.
- Works with what you have: reuse Claude Code, Codex or Gemini CLI as the model (no
  API key), or use…