Code comprehension, now with consequences.
A short, code-dependent quiz for the person who opened the PR. No trivia. No gotchas. No answers copied from the description they wrote five minutes ago.
Install the GitHub App, then sign in with GitHub. No password. No code to deploy. Mild accountability.
THE REVIEWER READS THE DIFF.
THE AUTHOR SHOULD TOO.
“LGTM” IS NOT A TEST STRATEGY.
Getting in
GateCheck uses your GitHub identity, so there is no separate password to forget—or paste into Slack.
Install the GitHub App, then choose your personal account or a GitHub organization from GitHub’s picker. Organization owners can install directly; members can request approval when their organization restricts apps.
Install & create account →Sign in with the GitHub account that can manage the installation. You’ll see every personal and organization installation available to that account.
Sign in to admin →How it works
The diff is processed in memory. The PR description is treated as an exclusion list, because repeating the ticket is not understanding the implementation.
A separate review pass throws out trivia, gotchas, ambiguous answers, and anything that does not reveal a meaningful misunderstanding.
Pass and the check goes green. Miss one and it goes red. Closing the PR is optional—accountability does not have to mean chaos.
A tiny taste
Questions focus on behavior, failure modes, data flow, security, and decisions that matter when somebody changes the code again.
Your app, your consequences
We ask only for the permissions the workflow needs. If you want the quiz to block merging, the setup screen walks you through making the check required. No sneaky Administration permission.
See installation permissions →Privacy without the interpretive dance
Changed code is held only while the quiz is generated. Queue jobs contain identifiers, not source. Application logs avoid PR content, questions, answers, and tokens. We keep aggregate PR count and diff size so one enthusiastic monorepo cannot eat the entire budget.
Reasonable questions
GateCheck does not train a model. Your selected AI provider processes the diff to create and review the quiz; choose a paid API plan with appropriate data-use terms for proprietary repositories.
Every candidate faces a separate quality review. It must be impactful, code-dependent, description-independent, fair, and grounded. Fewer than three survivors means generation retries instead of publishing junk.
Only if an installation administrator explicitly turns that setting on. By default, failure makes the check red and leaves the PR open for a human conversation.
It can. GitHub always shows the check, and your repository owner decides whether to make it required in a ruleset. We provide the setup link but do not seize Administration permission.
Go on, then
Deploy nothing. Configure in minutes. Blame nobody but the diff.