Linked issues
ContextReads Fixes #12, cross-repo refs and Jira or Linear keys, then checks whether the diff actually closes them. A 🧾 Linked issues block says what was addressed and what was not.
Most AI reviewers cry wolf, so people stop reading them. Bug Hunter reviews every pull request with your own model, makes a second pass try to disprove each finding, and only comments on the bugs that survive.
Open source under MIT. Gemini by default, or bring your own key for Claude, OpenAI, DeepSeek, OpenRouter, Ollama or any OpenAI-compatible model.
Something stirs on line 17…
Expired or unknown sessions return undefined, so s.user throws. The old code fell back to load(id); this change dropped it. Check for a missing entry before reading user.
if (!s) return load(id)?.user;
Bug Hunter · verified by the second look
Séance complete.
Bug Hunter marks the pull request the moment it starts and posts a single report when it’s done, so nobody has to wonder whether it’s stuck.
Open or update a pull request. A “The hunt has begun” status appears on it right away.
Your model reads the diff with explicit line numbers and writes plain technical findings.
A skeptical second pass tries to disprove every finding. What it can’t disprove stays.
Verified findings land on the exact lines, with one Séance Report on top and a haunting level on the pull request.
The model only ever writes plain findings. The costume is added by code after a finding has survived, so the technical content never depends on the theme.
Expired or unknown sessions return undefined, so s.user throws. The old code fell back to load(id); this change dropped it.
if (!s) return load(id)?.user;
Bug Hunter · verified by the second look
Reviewing the diff is the headline. These are the things that make it hold up week after week: context, memory, a budget, and a way to prove it still works.
Reads Fixes #12, cross-repo refs and Jira or Linear keys, then checks whether the diff actually closes them. A 🧾 Linked issues block says what was addressed and what was not.
When a change crosses components, the Séance Report adds a Mermaid 🧭 Signal flow diagram built only from participants that appear in the diff.
Reply @bughunter wrong: … on a review comment and the correction is stored per repo, then applied to later reviews. learnings lists them; forget drops one.
Every hunt records tokens and an estimated cost. Set MONTHLY_COST_CAP_USD and new hunts stop before the first model call once the cap is reached. The dashboard shows spend per repo and per hunt.
bughunter review --staged gives the same pipeline with no GitHub and no comments. Output as a human report, JSON, or a prompt-only list you can paste into a coding agent.
A fixture set with planted bugs and clean PRs runs the real pipeline against a mock provider. Precision, recall, false positives per clean PR and invalid positions are a CI gate, with no key or network.
gitleaks, semgrep and eslint run alongside the model where a checkout exists. Findings are advisory context, secrets are scrubbed, and a missing tool is skipped, never fatal.
Hunt history, repo auth mappings, learnings and installed repos survive restarts when DATABASE_URL is set, with an automatic in-memory fallback for local work.
POST /api/hunt with async: true returns a handle immediately and the client polls for the result, so a two-minute review cannot be cut off by a gateway.
Everything above is in the repo today — docs cover the CLI, costs, learnings, eval and linters.
Every finding is ranked by creature, always next to its real severity. The worst thing on a pull request sets its haunting level, which shows up on GitHub as a status check.
Try it: summon a few spirits and watch the level change.
All clear: no spirits detected. Status check passes
Everything in a pull request is untrusted: code, comments, titles and descriptions. Instructions aimed at the reviewer are flagged and ignored, and API keys never reach prompts, logs or comments.
This pull request description contains hidden text that tries to instruct the reviewer. It was ignored.
The review continued as normal.
Once the Séance Report is posted, n8n adds a row to the Hunt Ledger in Google Sheets and sends a Gmail alert when a pull request is haunted or possessed. Nobody has to copy anything across.
| Time | Repo | PR | Haunting level | Demons | Ghosts | False alarms |
|---|---|---|---|---|---|---|
| 10:42 | acme/api | 42 | Possessed | 1 | 0 | 1 |
Connect a repo in one click, or host it yourself. It’s a small Node server, and your keys stay in your own .env, never in prompts, logs or comments.
git clone https://github.com/dk3yyyy/bug-hunter.git
cd bug-hunter && npm install
cp .env.example .env # add your token + model key
npm run dev # http://localhost:3000
npm run cli -- review --staged # review first
Then open a pull request, or paste one into /connect to hunt it straight away.
Install the App on a repo, or run it locally against a branch. MIT licensed, no telemetry, and your keys and code stay where you put them.