Grip CLI
A CLI asks questions about a Git diff before push and uses a chosen model to assess how well the developer understands the change.
- 373 ★ on the repository
- Last commit
- BSD-3-Clause
Extended access
Why this level
- The CLI installs a Git hook and sends diffs and answers to the selected model provider.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/gripDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The CLI installs a Git hook and sends diffs and answers to the selected model provider.
This is third-party code. Review the repository files before installing.
What it does
Grip reads Git changes and asks about design, edge cases and validation. Developers answer in a terminal or browser whiteboard, and a model grades the responses. After installing its pre-push hook, a score below the threshold delays pushing. Without the hook, users can quiz staged changes or an entire branch. Providers include installed Claude Code, Codex and Gemini CLIs, hosted APIs and Ollama. The offline fake provider demonstrates the flow rather than evaluating answers meaningfully.
Who it is for. For developers and teams checking understanding of generated code before pushing changes.
Good fit when
- Explain a patch before pushing.
- Quiz the whole branch relative to main.
- Discuss the change on a browser whiteboard.
- Share a team passing threshold.
Not a fit when
- A quiz would replace code-security testing.
- The diff cannot be sent to the chosen model.
- Fake-provider scores would be used as real acceptance.
Example request
Show a Grip quiz for staged changes without installing a hook and explain what fake mode grades.Limitations
Python 3.11 or later and a selected provider are required; an installed model CLI can work without a separate API key. The model receives code changes and answers, so check permission to share those materials. Scores assess how a developer explains a change and do not replace tests or security review. The hook does not enforce a quiz for every push: `grip skip` bypasses one push, while CI and non-interactive runs are excluded.
How to disable. Remove Grip’s pre-push hook while preserving other project hooks, then uninstall the package. Inspect `.grip.toml` and retained results separately.
FAQ
When can push be blocked?
Only after hook installation with `grip init`.
How do I quiz the whole branch?
Use `grip quiz --branch`.
How do I open the whiteboard?
Run `grip whiteboard`.
Where is the threshold configured?
In `.grip.toml` through `passing_score`.
How do I allow one push?
`grip skip` lets the next push through.
Discussion
No questions or reviews yet.
Related
CLI toolsThe CLI replays Git changes as typing animations to present commits and working-tree edits in the terminal.
A CLI turns Git changes into a guided code walkthrough with questions and explanations written by your existing agent
GitUI is a terminal Git interface that runs operations asynchronously, keeping the interface responsive during Git work.
Before committing, compare several model-written messages and copy the chosen text into the Git interface you already use.
A CLI and MCP server that search package and repository source, read exact files and return examples with cited sources.
lazygit is a terminal Git interface for bisecting regressions: mark good and bad revisions while locating the faulty commit.
README in short
A passed diff is remembered. A retry reuses its questions rather than generating a fresh set.