Tool 02 · Code review · Gemma 4

Is this PR ready to merge?

Paste a pull request, even a draft, or a branch. Tell us what it should achieve, and get a ranked list of what’s wrong plus one prompt that fixes it.

  • Ranked by risk

    Every issue is tagged must fix, high, medium, low or nit, with the file, line and a concrete fix.

  • A clear merge call

    Safe to merge and ready to merge are decided from the findings, so the same issues give the same answer.

  • One prompt to fix it all

    Copy a single prompt into any AI coding assistant to work through every finding in order.

No PR handy? See a sample review

Public repos only. Draft, open, closed: any PR works, or a …/tree/branch or …/compare/main...branch link. Reviews can take a few minutes.

In a terminal, for private repos and local branches: oqgit review (or oqgit review 12 for a PR)

Sample review · Gemma 4

A pull request review that says what to do next.

Paste a PR, a branch or a compare link. You get findings ranked by risk, each with a failure scenario and a fix, a merge verdict, and one prompt to hand any coding agent.

  • Gemma 4, open weights

    gemma-4-31b-it reviews; the 26B mixture-of-experts model takes over when it's busy.

  • A verdict you can trust

    Merge calls are computed from the findings in code, so the same issues always give the same answer.

  • Built for free-tier keys

    Rotates keys, rests rate-limited ones, trims huge diffs and marks what it skipped.

Try it on your PRoqgit review 42 --strict

acme/uploader · #42

Add retry to failed uploads

Not safe to merge
  • Fails when
    Server returns 200 but the socket closes before the body is read → the catch block retries → the file is uploaded twice.
    Fix
    Only retry on network errors before a response, or on 429/5xx. Send an Idempotency-Key header.

Next · 4 of 5

Add skills to your agent

Hand-written playbooks that Claude Code, Codex, Cursor and others load when a task matches.