- Published by
- Tignex
- Home
- commitbrief.com
- Status
- v1.18.1 · stable
- License
- GPL-3.0-or-later
The problem
The cheapest bug to fix is the one you catch before anyone else reads the diff. Getting that first pass usually means signing up for a review platform, pushing the branch, and handing your source to a service — a lot of ceremony for a question you wanted answered locally, a minute after staging the change.
The approach
CommitBrief is a command-line tool that reviews what you point it at: the staged changes, a historic commit range, or a whole GitHub pull request. It runs on your machine, keeps no server, and sends no telemetry.
The model is your choice, not ours. It speaks to ten providers — Anthropic Claude, OpenAI, Gemini, DeepSeek, Mistral, Cohere, the Claude Code, Gemini and Codex CLIs — and to Ollama, which keeps the whole review on your own hardware. You bring the key — or run Ollama, or reuse the sign-in of a CLI you already use; nothing is rented from us.
What it is not
It is not a SaaS platform and there is no account to create. Install it from Homebrew, Scoop or `go install`, and if you stop using it, there is no account or data of yours left with us.
Frequently asked
- Does my code get sent to a server you run?
- No. CommitBrief runs on your machine, keeps no server component and sends no telemetry. Your code goes to whichever model provider you configured — and with Ollama it does not leave your hardware at all.
- Which model providers are supported?
- Ten: Anthropic Claude, OpenAI, Gemini, DeepSeek, Mistral, Cohere, the Claude Code, Gemini and Codex CLIs, and Ollama. Six of them take an API key you supply; Ollama needs none, and the three CLIs reuse the sign-in of a CLI you already use. Nothing is rented through us.
- What can it review?
- Your staged changes, a historic commit range, or a whole GitHub pull request.
- Can it block a merge or enforce a review policy?
- It can fail a CI job, which your forge can then require. `--fail-on` exits non-zero on a finding at or above a severity, `commitbrief guard` checks a review against a declarative `.commitbrief/policy.yml`, and the official GitHub Action wraps both. Whether a failed check actually blocks the merge is still a branch-protection setting on the forge.
Part of Tignex
CommitBrief is developed and published by Tignex, an independent open-source engineering organization. The project keeps its own name, identity and home; Tignex is the engineering behind it.