New: The State of Code Review 2026 — 77,949 PRs analyzed. Read the report →

FAQ

Who takes the quiz?

Anyone working on the pull request — the author as well as the reviewers. Reviewsaur posts a link on the PR, and whoever opens it takes the quiz; their result counts toward the required approvals.

We recommend the author plus at least one reviewer: the person who wrote the change and the person signing off both show they understand it. Every team works differently, though, so the setup is yours to choose.

What if a reviewer fails?

They get a fresh quiz — Reviewsaur generates a new set of questions about the same PR for them to try again, rather than re-serving the one they just failed. Each attempt is graded instantly with per-question feedback so they know what they missed, and they can keep trying until they pass.

The result page waits for the next quiz and links straight to it — usually in under a minute — so nobody has to go back to the pull request to find it. It is posted as a new comment on the PR too.

What happens when I push new commits?

The quiz stays the same. Reviewsaur makes the quiz and the walkthrough once, when the pull request is opened, so a small fix-up push does not throw away a quiz someone is already taking.

After a push, the PR comment shows how many new commits came since the quiz, with a link to regenerate for the latest commit. Any team member can use it, or click Regenerate quiz on the quiz page. Until someone does, the current quiz keeps working, passes still count, and the Reviewsaur Quiz check moves to the new commit. More in When a new quiz is generated.

Do reviewers need a Reviewsaur account?

Yes. To take a quiz, a reviewer must be signed in to Reviewsaur (via GitHub) and be a member of the team that owns the repository. Opening the quiz link while signed out sends them to sign in first, and someone outside the team can't take it. This is how each result is reliably attributed to a specific person.

The link itself contains a unique token, but that only identifies which quiz it points to — it doesn't grant access on its own.

Can an admin override a quiz?

Yes. Admins can reset a quiz, or manually mark it as passed or failed, from the quiz's responses view. Use this for edge cases — a trivial change, an outage, or a reviewer who demonstrated understanding another way.

What does the quiz cover?

Questions are generated from the PR diff and focus on the parts of the change that matter most; cosmetic changes (styling, copy, renames) get none. Each question has a category: Understanding, Risk, Architecture, Trade-off or Verification. How deep they go is set per repository by the difficulty setting: Easy questions can be answered from a single hunk, Hard ones need several parts of the change put together. Files matching your excluded paths are left out, and if every changed file is excluded, no quiz is generated and the check passes automatically. Very small changes — a typo, a comment, a version bump — get a shorter quiz, and on Pro they can skip the quiz altogether.

Does every pull request need a review?

No. Reviewsaur rates every change trivial, normal or complex from the diff alone and posts the verdict with a reason on the pull request. A trivial change — a typo, a comment, docs, a version bump, a config value, nothing that changes behaviour — can pass with a green check and no quiz.

Two rules pull a verdict back to normal: more than 100 changed lines, and any file matching the never trivial paths you set per repository. A title that says "trivial fix" changes nothing, an unknown verdict means a full review, and a review someone failed is never turned green afterwards. Letting trivial changes through is a Pro feature; on Free they get a shorter 2-question quiz.

What if I click "I don't know"?

If your admin turned the option on, every question has an I don't know button.

The question counts as wrong — there is no partial credit — but the correct answer and its explanation appear right away, and the question locks so it cannot be answered afterwards. The result page marks these apart from wrong guesses, so an honest gap reads differently from a bad answer.

Is my code used to train AI models?

No. We don't use your code or quiz data to train models, and our AI provider's commercial API terms exclude submitted data from model training. The diff is sent only to generate or grade a specific quiz and is discarded afterwards — see Where does your code go? for the full picture.

What exactly is sent to the AI provider?

The PR title and description, the diff (with your excluded paths stripped out first), the changed file paths, and recent commit messages. Your repository's name is not included in the prompt, and PRs over 50 files or 300,000 diff characters are rejected before any AI call. Grading a written answer sends only the question, its rubric, and the answer — not the diff.

How do I delete my data?

The full diff is never stored — it's discarded once the quiz is generated. Each question keeps a short excerpt of the code it is about (at most 40 lines), so the quiz can show it next to the question. These excerpts are deleted when the quiz is done: from a reviewer's quiz as soon as they finish it, and from the whole quiz when the pull request is closed or merged, or a newer quiz replaces it. None are kept longer than 30 days. If a closed pull request is reopened, Reviewsaur makes a new quiz, with new excerpts.

Quiz questions and results are kept while the repository is connected; removing a repo from Reviewsaur deletes its quizzes, responses, and settings with it. For account or team deletion, email [email protected].

Does it block merging?

Only once you make Reviewsaur Quiz a required status check in branch protection. See GitHub status check. Until then, quizzes are generated and linked but don't gate the merge.

What are the limits?

Free allows one active repository and 50 lifetime tests; Pro is unlimited. Full breakdown on Plans & limits.

Still stuck?

Email [email protected] and we'll help.