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.
"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 the whiteboard defense (not affiliated with grip)
Try it in 30 seconds
No hook, no account, no API key: the fake provider asks scripted questions offline.
pipx install grip-hook # or: uv tool install grip-hook
mkdir try-grip && cd try-grip && git init -q
echo 'def add(a, b): return a + b' > math.py && git add math.py
grip quiz --provider fake # five questions in your terminal
grip whiteboard --provider fake # the same, drawn in your browser
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. Sethook_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 Anthropic, any OpenAI-compatible API, or Ollama locally.
- Inside coding agents:
/gripin Claude Code, Codex, Gemini CLI, Cursor and others, and a gate that keeps the agent from pushing until you pass. - Out of the way when it should be: a passed diff is remembered, a retry reuses its
questions so only grading costs a call,
grip skiplets one push through, CI and non-interactive runs are skipped.
Installation
pipx install grip-hook # or: uv tool install grip-hook
Python 3.11 or newer, on Linux, macOS or Windows. This installs the grip command and a
git grip alias.
Quick start
cd your-repo
grip init # writes .grip.toml, installs the pre-push hook
git push # grip asks five questions first
grip init picks Claude Code, Codex or Gemini CLI as the model when one is installed.
Otherwise set ANTHROPIC_API_KEY, or see Providers.
Other commands you will use:
grip quiz # quiz your staged changes now, no hook needed
grip quiz --branch # quiz the whole branch since main: your pull request
grip whiteboard # defend the change in the browser
grip quiz --provider fake # try it offline with a scripted grader
grip skip # let the next push through
grip status # hooks, last score, configuration
The walkthrough follows one real change from
git commit to an accepted push.
Configuration
.grip.toml at the root of the repository, committed so the team shares one bar:
passing_score = 70 # 0-100
difficulty = "normal" # easy | normal | hard
provider = "claude-code" # auto | anthropic | claude-code | codex | gemini | openai | ollama
Every option, environment variables and the pre-commit framework hook are in the configuration reference.
Documentation
guilyx.github.io/grip: getting started, a walkthrough, coding agents, the whiteboard, how grip works inside, and the honest numbers on what the score does and does not measure.
Contributing
Issues and pull requests are welcome. See CONTRIBUTING.md for the development setup and SECURITY.md for reporting vulnerabilities and what data grip sends. This project follows a code of conduct.
Citation
If grip is part of a study or a course, please cite it; GitHub's "Cite this repository" button reads CITATION.cff.
License
BSD-3-Clause. Copyright (c) 2026, Erwin L.
Metadata
Release files for grip-hook 0.4.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| grip_hook-0.4.1.tar.gz | 129.0 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| grip_hook-0.4.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 224.5 kB
Release files / grip_hook-0.4.1.tar.gz
| Download URL | grip_hook-0.4.1.tar.gz |
|---|---|
| Size | 129.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d1112c876d437c446503485687cd1db3a0815a82a3f420f0d858f359589e5acf
|
|
BLAKE2b-256 checksum How to use checksums |
aa5f3d3cf3adf2a7295a3a4ff1e01ea56587b79c180b2c0ad791105f65303abf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logRelease files / grip_hook-0.4.1-py3-none-any.whl
| Download URL | grip_hook-0.4.1-py3-none-any.whl |
|---|---|
| Size | 95.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5ab6ce30f63773a825867709233754294c409dd02afa9a6d6b01c45afd9e069a
|
|
BLAKE2b-256 checksum How to use checksums |
e8a0ac851821529c6058fb73a966f6e35c9427b4bb8281f5dda259282ecee54a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logSecurity for grip-hook 0.4.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for grip_hook-0.4.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.