How a review works
Every push to a pull request in a project starts a review. Each agent reads the change, a checker re-reads what they found, and the result lands on the pull request.
What starts a review
- A pull request opens, gets a new push or is marked ready for review.
- Someone comments
@ionwarp review nowor@ionwarp review on. - Someone presses Re-run on the IonWarp / Review check in GitHub.
- Someone asks for one from a review’s page in the app.
Only repositories added as projects are reviewed. A newer push cancels the review still running on the older one.
Who reviews
The agents switched on for the project. Code Review runs every time. Security and API Performance run on every full review. The others join when the pull request touches what they watch, such as a workflow file for CI/CD. The eight agents lists each one’s trigger.
Then a checker re-reads each finding against the code. It can lower a finding’s severity or throw it out. It never raises one.
What the agents read
- The pull request’s diff at its head commit.
- The rest of the repository at that commit: every agent can read, search and list files, so Code Review can follow a changed function to its callers.
- Short facts about the repository, such as its language, runtime and tooling, read from the files that declare them on the base branch. No agent should flag code that is valid on your version.
- Your project notes, and the reasons your team gave when it dismissed earlier findings in the same files.
Some files are never read line by line:
| Kind | Examples |
|---|---|
| Lockfiles | package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lock, Cargo.lock, go.sum, any *.lock |
| Vendored code | node_modules/, vendor/, third_party/, Pods/ |
| Generated files | dist/, build/, generated/, *.min.js, *.d.ts, *.pb.go, *.snap |
| Binary files | Images, fonts, audio, video, archives, source maps |
| Fixtures | fixtures/, testdata/, snapshots/, goldens/, data files under data/ |
A pull request that changes only these gets a check titled Nothing to review, and no comment.
Severity and confidence
| Level | Means | On the pull request |
|---|---|---|
| 🔴 P0 · Blocking | Stop the line: fix it before merging. | An inline comment. The check concludes Action required. |
| 🟠 P1 · Should-fix | Should block this merge. | An inline comment. The check concludes Neutral. |
| 🟡 P2 · Noted | Real, and can wait. | Counted as a nitpick and listed under More → All findings. |
Each finding also has a confidence from 1 to 5. Below 2 it isn’t posted. Both floors are settings, and so are the check’s conclusions.
Later pushes
A push after the first review is reviewed on what it adds: the hunks new since the last reviewed commit, in the files the push touched. A merge from the base branch or a rebase adds nothing to read. After a force-push GitHub can’t compare, so the whole pull request is read again. A command or the app also reviews the whole pull request.
Re-reviews run Code Review and the agents whose files changed. From the fifth review of a pull request on, re-reviews run only Code Review and Docs.
Findings carry across reviews. Each keeps one id, like pr-42-k3j9x1, until it is fixed or dismissed, and the comment and check count the whole pull request, not only the last push.
Skipped pull requests
| The check says | Why | To review it anyway |
|---|---|---|
Skipped: draft PR | Drafts wait (ionwarp.review.review_drafts). | Mark it ready for review. |
Skipped: excluded author … | The author is in ionwarp.review.ignore_authors: Dependabot and Renovate by default. | @ionwarp review now |
Skipped: release / dependency PR (skip pattern match) | The title or branch matches ionwarp.review.skip_pr_pattern. | Commands are skipped too. Rename the pull request, or change the setting. |
Skipped: no reviewers enabled on this repo | Every agent is off for this project. | Switch one on. |
A skip never blocks a merge. Reviews turned off for one pull request (@ionwarp review off) or for a project (ionwarp.review.enabled) post nothing at all. When the workspace’s budget runs out, reviews pause instead: see Spend and budgets.