Docs
IonWarp docs
Last updated 2026-11-12
Everything IonWarp does on a pull request, and every switch that changes it.
Install
- Sign in with GitHub, Google or a code sent to your email. Your workspace starts its 14-day trial.
- Install the IonWarp GitHub App on your organization and pick repositories. Each repository becomes a project.
- Code Review, Security, and the agent of the page you came from are switched on. Switch the others on per project in the app.
- Open or push to a pull request. The review starts at once.
The agents: Code Review, Security Review, AI Architecture, Log & Errors, Docs Review, API Performance, SOC 2 Review, CI/CD Performance.
What a review posts
- One summary comment, edited in place on every push: what each agent found, by severity, with a fix prompt for your coding agent.
- Inline comments on the lines each finding points to, with a suggested change where one fits. Findings below
ionwarp.review.min_severitystay in the app. - The IonWarp / Review check. By default an open P0 makes it Action required, a P1 Neutral, and only P2s Success. A skipped review says why in the check’s title and never blocks the merge.
Severities: P0 blocks the merge, P1 should be fixed before merging, P2 is real but can wait. Drafts, PRs by Dependabot and Renovate, and release or dependency PRs are skipped by default.
Commands
Comment on the pull request. Only its author or a collaborator with write access can run them; anyone else gets no reply.
| Comment | What it does |
|---|---|
@ionwarp review now | Starts one review without changing the PR’s setting. Bypasses the excluded-authors list. |
@ionwarp review force | Reviews again even when the head commit has not changed. |
@ionwarp review off [reason] | Turns automatic review off for this PR. |
@ionwarp review on | Turns it back on and starts a review now. |
@ionwarp review status | Shows the PR’s review state. |
@ionwarp learn: <lesson> | Adds a one-line lesson every reviewer of this project reads from then on. |
@ionwarp ticket <description> | Tells us IonWarp did something wrong or confusing, with the PR attached. |
@ionwarp help | Lists these commands on the PR. |
wontfix: <reason> | A reply on a finding’s thread: dismisses it and keeps the reason. |
fixed | A reply on a finding’s thread: re-checks every open finding at the current head. |
🚫 Wontfix: <id> — why | A line in a top-level comment, no mention needed: dismisses that finding. |
Settings
Set them in the app for the whole workspace, and override any of them for one project. A project’s value replaces the workspace’s.
| Key | Default | What it does |
|---|---|---|
ionwarp.review.enabled | true | Turns reviews on or off. |
ionwarp.review.review_drafts | false | Reviews draft pull requests too. |
ionwarp.review.ignore_authors | dependabot[bot], renovate[bot] | Comma-separated logins whose PRs are not reviewed automatically. |
ionwarp.review.skip_pr_pattern | ^release[:/]|^chore\(release\)|^chore\(deps\) | A case-insensitive regular expression tested against the PR title and head branch. A match skips the review, commands included. Empty skips nothing. |
ionwarp.review.custom_context | (empty) | Notes every reviewer reads about this codebase: conventions, what matters, what to ignore. |
ionwarp.review.min_severity | P1 | The lowest severity posted on the pull request. Lower findings stay in the app, under All findings. |
ionwarp.review.min_confidence | 2 | The lowest confidence, on a scale of 1 to 5, a finding needs to be posted. |
ionwarp.checks.p0_conclusion | action_required | The check’s conclusion when a P0 is open. |
ionwarp.checks.p1_conclusion | neutral | The conclusion when the worst open finding is a P1. |
ionwarp.checks.p2_conclusion | success | The conclusion when only P2s are open. |
ionwarp.checks.not_reviewed_conclusion | action_required | The conclusion when a review could not finish. |
Session analytics
Ask your coding agent to add this block to the description of every pull request it opens, and to update it on later pushes. IonWarp reads it to measure two loops per project: the agentic loop, from the first prompt to the PR, and the CI/CD loop, from a push to the merge. The block is optional and never gates CI.
<details><summary>🛸 IonWarp Session Analytics</summary>
<!-- ionwarp:session-analytics v3 -->
```yaml
harness: Claude Code (Opus 5)
session_flow:
- step: plan
detail: read the prior plan docs; scoped the fix to one shared seam
min: 5
- step: implement
detail: one primitive replaced three divergent per-page copies
min: 30
- step: verify
detail: scoped vitest + a Playwright spec against the preview worker
min: 10
dev_testing:
- tool: vitest
duration_min: 4
cheatcodes:
- "prompt:one-primitive — named the shared seam before touching any page"
biggest_iteration_speed_improvement: faster scoped preview builds
```
</details>harness: the coding agent and model.session_flow: each step with a short detail and its minutes; their sum is the session’s length.dev_testing: the test tools run and for how long.cheatcodes: prompts or tricks that saved time.biggest_iteration_speed_improvement: what would have made the loop faster.
Fixing findings
- Fix prompt: every finding carries a prompt to paste into Claude Code, Codex or Cursor.
- Add to To-do: in the app, puts the finding on the project’s GitHub issue so it is not lost after the merge.
- @claude: if your team uses Claude on GitHub, IonWarp can ask it to open the fix as a pull request. You review it like any other.
IonWarp never pushes to your repository: the GitHub App reads code only. Security lists its permissions.