Try for free
DocsFixing findings

Fixing findings

Every finding comes with a prompt for your coding agent. IonWarp never pushes code itself.

Fix prompts

The same findings, three ways in:

  • 🔧 IonWarp Fix Prompt on each inline comment: one finding.
  • Agent prompt in each row of the review comment: one finding, with its id and the lines to answer it with.
  • More → 🔧 Fix prompt: every open P0 and P1 in one prompt. The check’s details carry the same text.
More → 🔧 Fix prompt
Apply the following fixes to this repo. For each item, verify against the
current code and only make the change if the issue is still present.

1. pr-42-k3j9x1 [P1] Admin route has no role check — require the admin role (api/routes/admin.ts:31)

Answer each in your IonWarp autofix round comment, its id first:
- ✅ Fixed: pr-42-k3j9x1 — what changed
- 🚫 Wontfix: pr-42-k3j9x1 — why

A coding agent with the GitHub CLI can read the prompt straight from the check:

Terminal
gh api repos/OWNER/REPO/commits/SHA/check-runs \
  --jq '.check_runs[] | select(.name == "IonWarp / Review") | .output.text'

Autofix rounds

After fixing, the agent posts one comment that answers each finding by id:

PR comment
⚡🛸 **IonWarp autofix round 1** — fixpack `a1b2c3d`
<!-- ionwarp:autofix-round 1 sha:a1b2c3d -->
- ✅ Fixed: pr-42-k3j9x1 — admin routes now require the admin role
- 🚫 Wontfix: pr-42-p0q8zz — the cache is per request by design
- ⏭ Skipped: pr-42-x1c4nn — needs a product decision
✅ **Verified:** `bun test` — 14 files green
  • The marker line is optional. Without it, the bold IonWarp autofix round N header and at least one answer line are enough.
  • 🚫 Wontfix: lines dismiss their findings at once, reason kept. ✅ Fixed: lines are claims the next review checks.
  • It must come from a person with write access. IonWarp ignores comments from bot accounts, so an agent posting through your GitHub CLI works.

Tell your coding agent

A few lines in your AGENTS.md or CLAUDE.md make this the default:

AGENTS.md
## IonWarp
After you open or push to a pull request, wait for the IonWarp / Review check.
Fix each open P0 and P1 it lists if it still holds, push one commit, then post
one IonWarp autofix round comment answering each finding by id.
Format: https://ionwarp.com/docs/fixing-findings#autofix

Add to To-do

In the app, Add to To-do puts a finding on the project’s GitHub issue, IonWarp To-do, as a checkbox with its file and pull request. IonWarp opens the issue the first time. The finding stays open after the merge, so it isn’t lost.

Hand to Claude

Hand to Claude (or @claude) adds the finding to the To-do and comments on that issue with @claude and the finding’s prompt. If your team runs the Claude GitHub app, it picks the issue up. The prompt asks it to check that the finding still holds, make the smallest fix, add a test that proves it, and open a pull request you review like any other.

Dismissing

Reply wontfix: <reason> on the finding’s thread, or dismiss it in the app. Either way the comment and the check update, and later reviews of the same files see your reason. If IonWarp keeps getting something wrong, teach it with a lesson, or tell us with @ionwarp ticket or at team@ionwarp.com.