AI code review
Have a model review your uncommitted changes or a GitHub pull request before anyone else does. Findings show up in a Review panel and as problems in the editor, and Fix with agent turns any finding into a chat that fixes it.
Review your changes
Run Ingot: Review Changes (⌘⌥⇧E, Ctrl+Alt+Shift+E). Ingot reviews git diff HEAD (staged and unstaged) plus new files that aren't git-ignored.
To review only what you are about to commit, with fixes you can apply and an optional block on serious findings, use the Agent Review button next to Commit: see Agent review before commit.
Review a GitHub pull request
Run Ingot: Review GitHub PR (⌘⌥⇧G, Ctrl+Alt+Shift+G) and enter #123 or the PR URL. Ingot reads the diff with the GitHub CLI (gh pr diff) if you're signed in to it; otherwise it uses a token from GH_TOKEN, GITHUB_TOKEN or the GitHub MCP server. Reading is all it does: nothing is posted to the pull request.
If it can't read the PR:
Could not read the pull request. Sign in to the GitHub CLI (gh auth login), set GH_TOKEN, or add a token to the GitHub MCP server.
The Review panel
The Review panel opens at the bottom with the findings grouped by file:
| Severity | Shown in the editor as |
|---|---|
| Critical, High | error |
| Medium | warning |
| Low | information |
- Each finding has a title, an explanation and its line. Click it to jump there.
- The status line reads
3 finding(s) in 2 file(s) · Ingot Fast, orNo problems found in 4 file(s). - The same findings appear in Problems with the source
Ingot Review, with a quick fix Fix with agent: …. - Clear findings removes them.
The review looks only at added lines and asks for real problems: bugs, crashes, security issues, data loss, race conditions, wrong logic, missing error handling. Style nits and praise are left out.
Fix with agent
Click Fix with agent on a finding. A new chat named Fix: <title> starts with the finding, its file and line, and asks for a minimal change. The edits arrive for review as usual.
Budget
A review uses a cheap model and a fixed budget, so it stays fast and inexpensive:
| Limit | Value |
|---|---|
| model calls per review | 3 |
| diff per call | 24,000 characters |
| findings | 40 |
Files that don't fit are skipped and listed in the status line. The model is the one in the ingot.agent.reviewModel setting, or else a cheap connected model such as Ingot Fast.
BUGBOT.md and /bugbot
Write your review guidelines in a BUGBOT.md file and Ingot uses them:
Look for missing awaits on promises.
Flag any SQL built with string concatenation.
Money is always integer cents, never floats.
| Where | Applies to |
|---|---|
.ingot/BUGBOT.md | the whole project |
<folder>/.ingot/BUGBOT.md | files under that folder |
.cursor/BUGBOT.md (also in subfolders) | read when the project keeps its .cursor setup (Import an existing setup) |
When a project has one, the /bugbot command appears in the / menu. It asks the agent to review your uncommitted changes against the guidelines and report each real problem with file, line and a suggested fix, without editing. Add a focus after it: /bugbot focus on auth.
Agent checks in your git hooks get the guidelines too: the root file plus those for the folders you changed.