Skip to content
IonWarpTry for free
All Agents

AI code reviewers for
GitHub pull requests

16 reviewers, each for one kind of problem: code, security, performance, docs and more. IonWarp reviews every pull request, and a planner picks the reviewers each diff needs.

All agents

Every reviewer IonWarp runs on a pull request, and what each one catches.

7 more reviewers
How it works

One install.
Every PR reviewed.

01 — Install

Install the GitHub App

Sign in with GitHub, install the app and pick the repositories it may read. No CI changes, no YAML.

02 — Configure

Choose your reviewers

Code Review runs on every pull request; a planner adds the other reviewers each diff needs. Add your team's rules in Settings or an ionwarp.json file.

03 — Review

Read one PR comment

Every reviewer that ran adds its findings to the same comment on the pull request.

What a review looks like

One comment per pull request.

Every finding has a severity (P0, P1 or P2), the file and line, and a suggested fix.

Reply @ionwarp learn: <rule> on any finding and every reviewer in the project reads that rule on the next review.

IonWarpbotexample review
IonWarp Review — PR #412
3 issues| 2 P1 1 P2
#SevIssueFile
1Second timeout parser reads a bare number as seconds, not millisecondslib/review-timeout.ts
2Import still points to the helper deleted by this PRlib/tasks.ts
3The fix patches one caller; the shared client still drops the errorapi/teams.ts
lib/review-timeout.ts
717273
−+ 
const timeoutMs = parseReviewTimeout(value);const timeoutMs = parseDurationMs(value);// shared parser owns supported units and validation
A second timeout parser reads numbers differently · AI Architecture

The new review-only parser duplicates the platform duration parser but treats a bare number as seconds instead of milliseconds. Use the shared parser and delete the duplicate.

Suggested fixAI fix prompt