main/a1f9e2/ai-pr-reviewer
a1f9e2feat: every PR reviewed in under a minute main

A careful first pass on every pull request.

AI PR Reviewer reads the whole change in context, not just the diff, and posts inline comments for bugs, security issues and style problems, with one-click fixes. Your reviewers open a PR that has already been cleaned up.

megicoder / checkout-service
Megicoder review 0 s

feat: add coupon to checkout #482Open

@priya wants to merge into main from feat/coupon6 files · +214 -38
Megicoder review requested
checkout/discount.ts+42 -6
54+export function applyCoupon(price: number, coupon: Coupon) {
55+ if (!coupon.active || coupon.expiresAt < Date.now()) return price
56+ // coupon.amount is in the same currency as price
57+ const total = price - coupon.amount
58+ return total
59+}
api/orders.ts+18 -4
110 const code = req.body.coupon
111 const db = await getPool()
112+ const rows = await db.query("SELECT * FROM coupons WHERE code = '" + code + "'")
Waiting for a human reviewer to approve.
CHANGELOG AI PR Reviewer

What it checks on every PR

Each finding has a severity, a short reason and, where possible, a suggested change you can commit from the PR.

Logic bugs and edge casesOff-by-one errors, negative totals, unhandled nulls, missing awaits, wrong comparisons and race-prone code.
Security issuesInjection, unsafe deserialization, secrets in code, missing auth checks, weak crypto and risky dependency use.
Performance trapsN+1 queries, work inside hot loops, unbounded reads and accidental full-table scans.
Your team rulesEvery rule in .megicoder/rules is checked against the change and reported with the exact line.
A PR summary for the human reviewerWhat changed, what is risky, what was fixed, and where to look first.

Repository context

It follows imports, types and call sites across the repo, so a change in one file is judged by how it is used elsewhere.

One-click suggestions

Fixes are posted as native suggestion blocks. Authors accept them from the PR without leaving the page.

Severity thresholds

Choose the minimum severity per repo. Lower findings go into the summary instead of the diff.

Fast enough to wait for

Most PRs get a full first pass in under a minute, before the author has switched context.

Ask follow-up questions

Reply to a comment to ask why, or ask for a different fix. The answer stays in the thread.

Re-review on push

New commits are reviewed incrementally. Resolved findings close themselves.

Suggestions, not decisionsAI comments are suggestions. Human reviewers approve and merge. Customer code is never used to train AI models and is processed only to produce the review.
git log --questions ai-pr-reviewer

Common questions

No. Megicoder can mark its own first pass as complete, but approval and merging always stay with a human reviewer on your git platform.

Linters check syntax and patterns in one file. AI PR Reviewer reasons about behavior across files: what a value can be at runtime, who calls a function and what breaks if it changes.

Yes. Each category (bugs, security, performance, style, rules) can be switched off or given its own minimum severity per repository.

git merge feat/first-review into main

Review your
first repo free.

One repository, AI review on every pull request, no time limit. Connect it in about five minutes and the next PR gets a first pass in under a minute.

Review 1 repo free