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

How it works

Reviewsaur's job is to make sure that when someone approves a PR, they actually understood the change. It reads every pull request, decides whether it needs a review, and quizzes the reviewer when it does; whether that quiz also blocks the merge is up to you (see Why a status check).

Looking for the short version with examples? See How it works. This page is the technical flow.

The flow

  1. A PR is opened. GitHub notifies Reviewsaur via webhook.
  2. Reviewsaur reads the diff. Files matching your excluded paths are skipped.
  3. Reviewsaur writes a walkthrough and rates the change. The walkthrough is a short review guide: what the PR does, the places to read closely (each with a question to check in the code, linked to the exact line), and the files that are safe to skim. It also judges the change trivial, normal or complex. A trivial change can skip the quiz entirely (Pro) or get a shorter one.
  4. A quiz is generated. Reviewsaur writes 4 questions about the parts of the change that matter most, from the diff alone; cosmetic changes get none. Each question has a category (Understanding, Risk, Architecture, Trade-off or Verification), digs as deep as the difficulty says, and comes in the format you chose (multiple-choice, short-answer, or mixed).
  5. A link is posted on the PR, and the Reviewsaur Quiz check is set to pending.
  6. A reviewer takes the quiz. Next to each question they see the part of the code it is about, plus the PR walkthrough and the changed files for context.
  7. It's graded instantly. Pass, and the check turns green. Fail, and they can retry.
  8. The check goes green once enough reviewers have passed (see required approvals). If you've made it a required check, that's also when the PR becomes mergeable.

When a new quiz is generated

Reviewsaur makes the quiz and the walkthrough once, when the pull request is opened. A new quiz is generated only when:

  • Someone asks for it. Any team member can regenerate from the link in the PR comment, or with Regenerate quiz on the quiz page. Reviewsaur makes a new quiz and walkthrough for the latest commit, and rates the change again, so the new quiz can be shorter, longer, or skipped. If you are halfway through the current quiz, it asks first.
  • A reviewer fails. They get a fresh quiz (see What if a reviewer fails?). If the failed quiz was from an older commit, the walkthrough is made again for the latest commit too.
  • The PR never got a quiz. If the first try did not produce one (for example, the PR was too large), the next push or reopen tries again.
  • The PR is reopened. Closing a pull request deletes the code shown next to the questions (see How do I delete my data?). When you reopen it, Reviewsaur makes a new quiz so the code is back. The walkthrough is kept if it is for the same commit.

What happens when you push new commits

A push does not replace the quiz. The current quiz keeps working, and anyone who already passed still counts toward the required approvals. Reviewsaur:

  • Moves the Reviewsaur Quiz check to the new commit, so a required check never gets stuck waiting.
  • Marks the PR comment as out of date — it shows how many new commits came since the quiz, and a link to regenerate for the latest commit. If the new commits are small, you can keep the quiz you have.

Every PR comment shows when the quiz and the walkthrough were made, and from which commit (times in UTC). The quiz page shows the same, plus a note when the PR has newer commits.

When a quiz is replaced

When a regeneration replaces a quiz, the old one can no longer be submitted, even if someone already opened it. The existing comment on the PR is updated with the new link, so the PR still has one quiz comment. The new quiz tries not to repeat questions from earlier quizzes on the same PR. A regenerated quiz counts toward your plan's quiz limit, like any other.

When no quiz is generated

  • The PR is opened by a bot (dependabot, renovate, any [bot] account). It gets a green check and no quiz or comment.
  • The change is trivial and skipping trivial changes is on (Pro). This never happens right after a failed attempt: a failed review always gets a new quiz.
  • The PR is too large, every changed file is excluded, or the quiz limit is reached. See Plans and limits.

Why a status check

The quiz only blocks a merge if you've added Reviewsaur Quiz as a required status check in branch protection. That's intentional: Reviewsaur can't change your repo's protection rules for you, so you stay in control. Set it up once per repo — see GitHub status check.

What it's solving

  • Rubber-stamp reviews. A large share of reviews are approved in under five minutes. A quiz makes “LGTM” mean something.
  • AI-generated code. When a diff was written by a model, the human approving it should still understand it. The quiz checks that.
  • Knowledge silos. Quizzes spread understanding of a change across the team, not just its author.

Who sees what

  • Reviewers take quizzes and see their score and per-question feedback.
  • Admins can view all responses, reset a quiz, or manually mark it passed/failed. On Pro they can also give one person a different "I don't know" setting (per-developer settings).
  • Authors see the check status on their PR. They can take the quiz too; a pass counts toward the required approvals.

For the full set of knobs, head to Quiz settings.