SlopBlock GitHub App

Know the code before it ships.

SlopBlock posts a short quiz based on the actual diff. If the pull request matters, the author has to pass it before the merge goes through.

Install on GitHub Sign In Try Demo

Your second pair of eyes

Catch what speed
makes you miss.

Moving fast is fine. Blindly merging is the problem. When you're deep in a feature, especially with AI in the loop, it's easy to ship code you only half read. SlopBlock slows you down just long enough to prove you actually know what changed.

Review your own blind spots

The questions come from the diff, not from a generic list of best practices. They tend to hit the parts you'd otherwise skim.

Understand AI-generated code

If Copilot or Cursor wrote half the PR, you should still be able to explain it. This gives you a quick gut check before it lands.

Skip the obvious, quiz the risky

Docs, renames, and low-risk changes pass through automatically. The quiz shows up when a PR looks worth slowing down for.

solo workflow

$ git push origin feat/auth-refactor ✓ Lint passed ✓ Tests passed ● SlopBlock — 3 questions about your changes # What does the new refreshToken() fallback do? # A) Returns null and logs out # B) Retries once, then returns the cached token ✓ # C) Throws an AuthError ✓ Correct. The retry-then-cache strategy avoids forcing a re-login on transient failures.

Enforce understanding at merge

No one merges what
they can't explain.

Code review can catch bugs. It does not always catch the author nodding along to code they barely understand. SlopBlock adds one more check before merge: can the person who opened this PR explain what changed and where it might break?

Stop rubber-stamped AI code

If AI wrote part of the pull request, the author still has to own it. Passing the quiz is a simple way to prove that.

Configurable strictness

Routine changes can get a lighter touch. Auth, payments, and infra can get stricter checks. You control that per repo.

Works alongside code review

SlopBlock runs as a status check. Reviewers still review. This just makes sure the author came prepared.

team workflow

PR #318 feat: migrate payments to Stripe v4 author: @junior-dev reviewers: @lead, @security ✓ CI / build ✓ CI / test ✓ @lead approved ● SlopBlock — Awaiting author quiz (3 questions) # Merge blocked until @junior-dev passes # Questions focus on changed webhook signature and idempotency key logic

How it works

Reads the diff

Questions are tied to the changed lines in the PR, not generic trivia.

Skips the obvious

Docs, renames, and trivial changes pass through without extra noise.

Quizzes the author

The author gets a short multiple-choice quiz about behavior, risk, and implementation details in the PR.

Unblocks the merge

Pass the quiz and the status check goes green. Miss a question and retry based on your team's policy.

For solo builders and teams

Stop merging code
nobody can explain.

View on GitHub Sign In Try Demo