Review the change.
Understand the codebase.

OpenReview reviews pull requests using your whole repository, not only the diff. Every finding quotes the code it depends on, and nothing is posted until it has been verified.

Read the quickstart →Self-host it →

OpenReview

Acme

@dana

Acme

Pull Requests

Updating automatically

acme/shop #42

completed

GitHub · Acme · github.com · Repository ID 482113

Reviewed revision 9f3c2e1a7b40d6c1 · Oct 14, 2026, 2:03 PM UTC

Show cart totals in dollars · @dana · View pull request

feature/dollar-totals → main

Changes

Exact base…head comparison at 9f3c2e1a7b40 · 2 files

src/cart.ts modified · 1 finding

`@@ -1,6 +1,7 @@`
1	1	`// Cart arithmetic. Prices are stored as integer cents.`
2	2	`export function total(cents: number, qty: number) {`
3		`- return cents * qty;`
	3	`+ // Show totals in dollars.`
	4	`+ return (cents * qty) / 100;`
		🔴 P0 total() now returns dollar value instead of cents, breaking charge() expectations total() now divides by 100 and returns a dollar value, but charge() in src/billing.ts still passes it to the payment provider as amount, which its own comment says is integer cents.
4	5	`}`
5	6
6	7	`export function itemCount(lines: { qty: number }[]) {`

test/cart.test.ts modified · 1 finding

`@@ -3,5 +3,5 @@ import { total } from "../src/cart";`
3	3	`test("total multiplies price by quantity", () => {`
4		`- assert.equal(total(1250, 2), 2500);`
	4	`+ assert.equal(total(1250, 2), 25);`
		🟡 P2 Updated test asserts the dollar value, so the billing regression passes CI The expectation was changed to match the new unit. No test covers charge(), so the suite stays green while the provider receives dollars.
5	5	`});`

Verdict

Needs changes · computed from the score, unresolved findings and review coverage

Confidence score

2/5 · confidence that the change is safe to merge

The change silently alters a unit that billing depends on; payments would be sent in the wrong unit.

Reviews pull requests on

GitHub
GitHub Enterprise
GitLab
Azure DevOps
Bitbucket
Gitea
Perforce

Evidence

Evidence on every finding

Each issue cites the exact lines it depends on, pinned to the commit, with a committable suggestion when the fix is small. A finding that cannot quote the reviewed revision is dropped.

Learn how reviews work →

Verified findings

🔴 P0 total() now returns dollar value instead of cents, breaking charge() expectations

src/cart.ts:4 · 95% confidence · Verified at this revision · Current status: open

total() now divides by 100 and returns a dollar value, but charge() in src/billing.ts still passes it to the payment provider as amount, which its own comment says is integer cents.

Impact: Payments would be sent in the wrong unit: a $25.00 cart is charged as 25 cents, or rejected as a non-integer amount.

src/cart.ts:4
  return (cents * qty) / 100;

src/billing.ts:2
// Payment provider amount is integer cents.

src/billing.ts:3
  return provider.charge({ amount: total(cart.priceInCents, cart.quantity), currency: "USD" });

Suggested fix: Keep total() in cents and format dollars where totals are displayed, or convert back to cents in charge() before calling the provider.

Summary

One summary, kept current

A single summary comment with an overview, changed files, issues, a confidence score and a sequence diagram is updated as the pull request moves. New pushes are reviewed against what changed.

See what a review posts →

Review summary

Summary of changes

src/cart.ts: total(cents, qty) now returns dollars (cents * qty / 100) instead of integer cents.
test/cart.test.ts: the expectation was updated to the dollar value.

Affected areas

src/billing.ts calls total() and sends the result to the payment provider as integer cents.

Recommendation

Request changes. Keep total() in cents and convert to dollars only where totals are displayed.

Review history

Oct 14, 2026, 2:03 PM UTC · 9f3c2e1a7b40d6c1 · completed2 findings · Score 2/5
Oct 14, 2026, 1:41 PM UTC · 4b7d0a2c91e5f377 · completed1 findings · Score 3/5

Chat

Ask your codebase

Chat, the API, MCP and Slack all answer questions with citations that must match the indexed source.

Learn about codebase chat →

You · Oct 14, 2026, 2:10 PM

Where is the checkout total computed, and which callers depend on it?

OpenReview · Oct 14, 2026, 2:10 PM

Totals are computed by total() in integer cents [1], and charge() passes them straight to the payment provider [2]. Any change to the unit of total() changes what the provider is charged.

acme/shop:src/cart.ts:2 @ 9f3c2e1a7b40
```
  return cents * qty;
```

acme/shop:src/pay.ts:2 @ 9f3c2e1a7b40

export const charge = (c: number) => provider.charge({ amount: total(c, 1) });

Fixes

Fix with your agent

Hand findings to Codex, Claude Code or Cursor Agent on your machine, or ask @openreview for a validated fix.

Set up the agent bridge →

total() now returns dollar value instead of cents, breaking charge() expectations

🔴 P0 open

acme/shop #42 · src/cart.ts:4 · 95% confidence

Suggested fix: Keep total() in cents and format dollars where totals are displayed, or convert back to cents in charge() before calling the provider.

Open in Cursor Open in Claude Code Open in Codex Opens your agent with the prompt pre-filled; nothing runs until you send it.

Portable prompt for Codex, Claude Code, or Cursor

Fix verified OpenReview finding in acme/shop PR #42 (revision 9f3c2e1a):
[critical] src/cart.ts:4 total() now returns dollar value instead of cents…

Analytics

See what reviews are worth

Track reviews, verified findings, addressed rate, time saved and model cost by repository, team and author, and export it as CSV.

Read the quickstart →

Total PRs24

Total Reviews37

Verified findings19

Model cost$6.82

Review activity

10-01

10-02

10-03

10-04

10-05

10-06

10-07

10-08

10-09

10-10

10-11

10-12

10-13

10-14

Findings by severity

critical2

high5

medium8

low4

Reviews and findings per day

ReviewsFindingsAddressedmax 6 · 10-01 – 10-14

Reviews and findings per day
Day	Reviews	Findings	Addressed
10-01	2	1	0
10-02	3	2	1
10-03	1	0	0
10-04	4	2	1
10-05	2	1	1
10-06	0	0	0
10-07	0	0	0
10-08	3	1	1
10-09	5	3	2
10-10	2	1	1
10-11	4	2	1
10-12	6	4	2
10-13	3	1	1
10-14	2	1	1

Built for reviews you can trust

Incremental re-reviews

New pushes are reviewed against what changed, and threads for fixed findings resolve themselves.

Configuration as code

Rules and settings live in .openreview.json, read from the base branch so a PR cannot weaken its own review.

Many providers

GitHub, GitHub Enterprise, GitLab, Azure DevOps, Bitbucket Cloud and Data Center, Gitea and Perforce.

Your model, your budget

Bring Anthropic, OpenAI or a compatible endpoint. A hard inference budget and per-task usage accounting keep spend predictable.

How it works

01
Index the repository
OpenReview parses your default branch into files, symbols and a cross-file call and import graph, with optional semantic embeddings.
02
Investigate each change
The diff is read alongside its callers, tests, past findings, your rules and any linked requirements, by specialists or a tool-using agent.
03
Verify before posting
A finding needs exact quotes from the reviewed revision and survives an independent check. Unsupported claims are dropped.
04
Learn from your team
Reactions, feedback and recurring human review comments become memory that your admins can inspect and control.

Run it on your infrastructure

Your Next.js host, your Convex backend and your model provider. Code goes only to the model you configure, and secret-looking values are redacted first.

Read the self-hosting guide →

Terminal

$ pnpm install
$ CONVEX_AGENT_MODE=anonymous pnpm exec convex dev --once
$ pnpm setup:local
$ pnpm backend
$ pnpm dev

Self-hosted or cloud

Aspect	Self-hosted	Cloud
Where it runs	Your Next.js host and Convex backend	A hosted OpenReview deployment
Model and keys	Yours, with your own budget	Provided by the operator
Review limits	None	Plan quota per seat
Setup	Self-hosting guide	Sign in and install the app

Questions

Does OpenReview run our code?

No. Reviews read source and never execute it. Test results appear only when a paired runtime worker records them for that commit.

Where does our code go?

Self-hosted, it stays in your Convex deployment and goes only to the model provider you configure. Secret-looking values are redacted before model calls.

Can a pull request turn its own review off?

No. Repository configuration is read from the base branch, and admins can lock settings.

Will it flood our PRs with comments?

Findings must pass confidence, severity and evidence thresholds. You choose the maximum comment count, strictness and categories, and learned preferences reduce repeat noise.

Which models are supported?

Claude and OpenAI models, or any OpenAI-compatible endpoint, with per-task model routing.

Try OpenReview now.

Get started Read the quickstart →

Review the change.Understand the codebase.