Try for free
DocsThe comment and the check

The comment and the check

Three things on every reviewed pull request: one comment, a thread on each line that needs a fix, and one check.

The review comment

One comment per pull request, edited in place as agents finish and on every push. Nothing piles up.

The comment's outline
## ⚡ IonWarp Review — PR #42 · round 2
🟠 2 open · 🟡 3 nitpicks · ✅ 1 fixed

▸ one fold per P0 and P1: Description, Evidence, Agent prompt
[View in IonWarp]

▸ More
    📋 All findings     every finding, open and resolved, P2s too
    📝 Walkthrough      what each changed file does
    🔬 Swarm            each agent's model, result, cost and time
    🔧 Fix prompt       every open P0 and P1, in one prompt
    🧭 Review log       what happened, and when

🔁 @ionwarp review now to re-run · @ionwarp help for commands · Last reviewed a1b2c3d

The round shows from the second review on. On a very large review the More folds drop from the bottom first, so the comment stays under GitHub’s size limit.

Inline comments

Each P0 and P1 lands on its line when that line is in the diff, one comment per line. A comment holds:

  • the level, such as 🟠 P1 · Should-fix, and the agent;
  • the title and why it matters;
  • a GitHub suggested change, when the fix is eight lines or fewer;
  • 🔧 IonWarp Fix Prompt, to paste into your coding agent;
  • the evidence: the lines it read and what they show.

Reply on the thread to answer it: replies lists what IonWarp understands.

The IonWarp / Review check

One check per head commit. Its title says where the pull request stands, and its conclusion follows the worst open finding:

The check's states
StateConclusionTitle
An open P0action_required1 P0 + 2 P1 open · loop closes at 0 open (fix or `wontfix:`)
An open P1, no P0neutral2 P1 open · loop closes at 0 open (fix or `wontfix:`)
Only P2s, or nothingsuccess0 open · 1 fixed · loop closed
Some agents didn’t answerneutralIonWarp review: 3 of 4 reviewers delivered
The review didn’t runaction_requiredIonWarp did not review this push
A newer push replaced itneutralIonWarp review cancelled
Skipped by a ruleskippedSkipped: draft PR
Nothing reviewablesuccessNothing to review — …

Settings change the conclusion for an open P0, an open P1, only P2s, and a review that didn’t run. Answering a finding, with a fix or a wontfix:, updates the check without a new review.

To block merges on a P0, make IonWarp / Review a required check in your branch protection. GitHub counts success, neutral and skipped as passing.

The check’s details also carry the Fix prompt while a P0 or P1 is open, so a coding agent can read it from GitHub’s Checks API: see Fixing findings.

Reactions

👀 on the pull request (or on your comment, when a command started the review) means a review started. 👍 on the pull request means it finished with no P0.