Pull request review you can read the source of.¶
open-nitpick reviews pull requests with the model provider you choose and can post inline comments. Run it as a GitHub Action, in any CI system, from an agent, or against local changes before a pull request exists. The reviewer is self-hosted; review input is sent to the model provider you configure. Choose a local provider to keep review input on your machine.
Review changes · Configure models and policy · Use from an agent · All workflows · Trust model
Read the provider guidance before selecting a hosted endpoint, inspect the measurements, or read the source on GitHub.
# A release binary, or `go install …/cmd/nitpick@latest` with Go 1.26.0.
v=$(gh release view --repo jdziat/open-nitpick --json tagName -q .tagName)
os=$(uname -s | tr 'A-Z' 'a-z'); arch=$(uname -m | sed 's/x86_64/amd64/;s/aarch64/arm64/')
curl -fsSLo nitpick "https://github.com/jdziat/open-nitpick/releases/download/$v/nitpick_${v}_${os}_${arch}"
chmod +x nitpick && sudo mv nitpick /usr/local/bin/
export LLM_PROVIDER=openrouter
export LLM_MODEL=z-ai/glm-5.3-flash
export OPENROUTER_API_KEY=sk-or-...
nitpick review # reviews your uncommitted changes
Any model, different models per job
Eighteen providers, with Synthetic and OpenRouter built in, plus any OpenAI-compatible endpoint, Ollama and llama.cpp. A cheap model triages and a strong one reviews. An expert pass can overrule either. Configuration →
Prompts you can print before you pay
Path-scoped instructions live next to the code they describe. nitpick explain-config shows the exact prompt a file would get. Instructions →
Context in both directions
Reviews include the functions and types used by changed code. You can also enable caller context to check code that depends on your changes. Related context →
A trust model, written down
The reviewer reads policy from the base revision and uses trusted linter settings. By default, pull-request configuration cannot override provider endpoints or credentials. Trust model →
Linters as evidence, not noise
Thirty-three, configured from outside the tree they read. golangci-lint and ruff ship enabled, twenty-four more run whenever they are installed, and eslint, semgrep and five others wait until you name them. Their output goes to the model for triage instead of into the pull request. Analyzers →
Measured, mistakes included
Five corpora and a judge-free harness. The findings document records the instrument bugs found along the way, including the one that forced a retraction. Findings →
How a review runs¶
- The change is read from GitHub or a local checkout, and the policy it is reviewed under comes from the base revision, not the branch.
- Analyzers that are installed run against the changed lines, isolated from the tree, and their output becomes evidence.
- Files are bundled into batches under a token budget, with related context attached: what a changed line calls by default, and who calls what the change redefined when the caller walk is switched on.
- Each batch is reviewed by the model the route selects. A triage model merges and filters. An optional expert pass refutes.
- The review is posted as inline comments, with a summary that lists every file not reviewed, every analyzer that did not run, and every finding that was discarded and why.
The quickstart uses OpenRouter with GLM-5.3-Flash, the reviewer this repository uses in CI. You can spend nothing first: nitpick explain-config prints what a review would send without sending it, and LLM_PROVIDER=ollama runs against a local model. Why, and the alternatives →