A local-first PR review harness
Good code.
Clear intent.
A way forward.
Your agent writes the software. Ferretta reviews the pull request—checking the code, questioning ambiguity, and making tradeoffs visible.
Pure Go. Your hardware. Evidence tied to the commit.
$ ferretta demo --outcome question
CLARIFICATION_REQUIRED
The expected behavior for an empty selection is unclear.
PROPOSED-EmptySelection-v1::
Should an empty selection return an empty result or a validation error?
One binary. A small start.
Meet your next reviewer.
macOS & Linux · Apple Silicon, ARM64 & AMD64
curl -fsSL https://ferretta.cc/install.sh | shPublished releases only. Inspect the script, choose a version, or build from source →
Launch prerequisite: a published release. Draft releases cannot be installed.
After the pull request
Review with a reason.
Ferretta joins when there is something concrete to review. Your earlier work with an implementation agent stays yours.
- 01
Start from the commit
Prepare a detached worktree at the submitted revision. Load trusted checks and a bounded local model policy.
- 02
Follow the evidence
Let the reviewer read files, run your checks, and examine whether the implementation fits the intent.
- 03
Make the next step clear
Get findings, a question, or an earned LGTM—alongside major tradeoffs and model provenance.
Small, on purpose
Ambition with
an honest boundary.
A bounded, advisory review
Ollama tool use and thinking. GitHub App identity. Human-readable reports. Durable PR intake with SQLite.
A coordinated review service
Model waves, OpenRouter, budgets, comment conversations, repairs, and automatic merging remain planned. The current service collects work; it does not run reviews.