It opens more pull requests in a day than you can read in a week. RUNOUT turns each one into five sharp questions about the change. The code with your name on it stays code you can defend.
Your agent wrote it. The tests passed. You approved it in forty seconds. Six weeks later it pages you at 2am, and you read your own file like a stranger's.
Four engineers, an agent each, one codebase. Every pull request got an approval. Not one of them got a reader.
Nobody reads a 900-line agent diff at 6pm on a Friday. People skim it, they approve it, and the codebase gets one more room that nobody has walked into.
RUNOUT asks the small question the approval was meant to answer: do you know why this changed? Five questions. Two minutes. No queue, no blocking check, no comment thread that dies over the weekend.
A quiz belongs to the repository, not to the person who opened the pull request. So you can take the quiz on a change you did not write. It is the fastest way to learn what a teammate shipped.
Pick an answer. Some of these come from your own pull requests, some from a teammate's, and one from the Friday quiz on the whole repository. None of them ask whether you can read code.
It's about the trade-off. Fixed retries can amplify an outage; backoff capped at 30 s eases off exactly when the provider is already struggling. RUNOUT scores the why — not a definition you could paste from the docs.
Want questions like this about your code?
Try for free →Connect the GitHub App. When you open a pull request, or mark one ready for review, RUNOUT reads the diff. Then it explores the code around the diff to find what actually matters.
Five questions for a small change, ten for a big one. Each one asks why a decision was made, or what breaks if an invariant fails. Never “what does this method do.”
Miss a question and the explanation appears on the spot. About half of your next quiz re-tests the areas where you are weakest.
And on Friday morning, every repository gets one quiz about itself as a whole — so a quiet week still asks you something.
Every finished quiz becomes a point: the share of questions you got right, with a rolling mean over the top. One line per repository, because a repo you stopped following falls behind on its own. A falling line means you ship faster than you understand.
If you own the account, you see these lines for the whole team. That is how you find the repository everybody approves and nobody understands.
Connect a repository. Your next pull request comes back with five questions.
Already have an account? Log in