New an AI review that picks what you need to read

Review pull requests
like the reviewer you are.

PRway is a desktop app for the human side of code review. It walks you through a GitHub PR chunk by chunk, explains how the code worked before, and shows you only the chunks that matter.

Download PRway How it works

Free · macOS, Windows and Linux

PRway

Charge late fees once per billing period #482

ana wants to merge late-fee-once into main · +142 −61 · 9 files · AI: Work · you@acme.dev

GuidedFilesCode

5/16 chunks · 3/9 files

schema.ex2/2

late_fees.ex⚠1/4

L41–58 def apply/2 ⚠

L77–90 defp period_of/1

L112–131 def backfill/1

invoice_worker.ex0/3

config.exs1/1

late_fees_test.exs0/6

notifications.ex0/2

13 chunks the AI review says you don't need to read are pre-approved · see them in Files

lib/billing/late_fees.ex High risk☐ Side by side

File 2 of 9 core logic: moves the "once per period" rule from the worker into apply/2. ▸ summary · ⚠ 1 finding

⌃ 36 hidden lines+10 linesShow all

▾Chunk 1 of 4L41–58Medium3 leftApprove & nextComment

medium A retried job can charge the fee twice L43👎 💬
The check at L43 and the insert at L46 aren't atomic, and nothing unique covers (invoice_id, period): two runs for the same invoice both insert.
checked: late_fee.ex:12 · 20251102_late_fees.exs:8 · invoice_worker.ex:52

Fees are now skipped when one already exists for the period, instead of when the invoice was "notified".

4141 def apply(invoice, now) do

42 if invoice.notified_at do

42 period = period_of(now)

43 unless Repo.exists?(fee_for(invoice, period)) do

4344 %LateFee{invoice_id: invoice.id, amount: fee_amount(invoice)}

45 |> LateFee.changeset(%{period: period})

4446 |> Repo.insert()

4547 end

4648 end

⌃ 28 hidden lines+10 linesShow all

Guided review

One chunk at a time,
in the order that makes sense.

PRway reads the PR first and gives you a reading order: the core change, then what depends on it. You go chunk by chunk and approve as you go. Only you see the approvals, and new commits don't reset them.

A plan before you start

What the PR is for, which files carry the change, and what's not explained by the description.

Only what matters

An AI review reads the whole PR and decides chunk by chunk what you need to read. Docs, tests that follow the code, renames and wiring are pre-approved, and you can spot-check them any time.

A review that shows its work

Up to five findings, each at a line, with the callers, schemas and tests the AI read to confirm it. No style nits, and no findings is a fine answer.

Teach it what's noise

Mark a hint 👎 and say why. Later notes skip that kind of point and follow your reason as a rule, so the AI gets less picky over time.

A real code view

Every PR is checked out locally. Go to definition, find references and open any file at the PR's head, like in your IDE.

Ask about any line

Click a line number and ask in chat. The chat can read the rest of the repository, so it looks up callers and tests itself.

Background

Know how it worked
before the PR.

Most tools summarize the diff. PRway traces the core of the change through the code, back to the controllers and jobs that reach it, and explains the old behaviour and the business rules the PR changes, with links to the code and to the earlier PRs that shaped it.

Cached, not re-read. Traces and function summaries are kept and reused, so the next PR on the same code is fast.
Editable. Fix a function summary once and your version wins from then on.
It sharpens the review. Chunks outside the core change can be pre-approved, so the guided view only shows what matters.

Late fee per period · before this PR

A late fee was charged when the invoice worker saw an unpaid invoice with notified_at set, and the worker cleared that flag after charging. invoice_worker.ex:88

Retries after a crash could charge twice, which is why #311 added the 24h guard in the scheduler.

What changes

The rule moves into LateFees.apply/2 and keys on the billing period instead of the flag.

Watch out

Backfill reuses apply/2 with now in the past: periods are computed from it, so old invoices get their own period.

Your AI

Your Claude subscription.
One per organization.

PRway doesn't sell seats or tokens. It uses the Claude Code you're already signed in to, or an Anthropic API key.

Work and personal kept apart. Link each GitHub organization to its own account; everything else uses your default.
Always visible. Every PR shows which account the AI uses, and everything it writes says who wrote it.
Your prompts. Add context about your domain and conventions per repository, or share it with the team in .prway.json.

How it works

From "review requested" to submitted.

Sign in with GitHub

Pick a repository. Your PRs, the ones waiting for you and drafts are grouped for you, with notifications when someone needs you.

Read the plan

The summary says what the PR does and what changed in the rules. The guide gives the reading order; the background, the history.

Review chunk by chunk

Read only what the AI review left for you, with what to check and any findings in the chunk. Approve, comment or ask; progress survives new commits.

Submit to GitHub

Your comments go out as one review: approve, request changes or comment. Threads and replies stay in sync.

Privacy

Runs on your machine.

There's no PRway server. Your code is cloned to your computer, and only the PR's material goes to the AI account you chose.

Tokens in your keychain. The GitHub token and API keys are stored with the operating system's encryption, never in plain files.
Read-only AI. When the chat reads code, it can only read the PR's checkout, nothing else on your disk.
Plain folders. Clones and worktrees live in ~/.prway, so you can open any PR in your editor.

Review your next PR with PRway.

Free for macOS, Windows and Linux. You need a GitHub account and Claude Code or an Anthropic API key.

Builds aren't code-signed yet: on macOS, right-click the app and choose Open the first time; on Windows, choose "More info → Run anyway".

One chunk at a time,in the order that makes sense.