First hackathon
ShellHacks 2026
We're three college students who build at hackathons together. At ShellHacks 2026 we built Repro in 36 hours, and it won the Microsoft prize.
The Repro pipeline: Ingest, Detect, Reproduce, Diagnose, Repair, Verify.
Repro reproduces every scanner warning in a sandbox and fixes only what it proves. A person merges.
Proof, not promises. Repro reproduces every scanner warning in a sandbox and fixes only what it proves; a person merges.
Clones the target into a fresh workspace, pinned to one commit.
Deterministic scanners; no model decides what counts as a finding.
Re-runs each finding's reproduction command in a sandbox, keeps only what shows the problem.
Groups findings by root cause, proposes a fix per group.
Edits files through sandboxed tools; the diff comes from git.
Tests + reproduction re-run, an adversarial check tries to break the fix; a person decides whether to merge.
ShellHacks 2026
Microsoft prize · ShellHacks 2026
Repro at ShellHacks 2026
Original (non-fork) public repos across the three of us
Primary languages across those repos
Combined GitHub contribution calendars
Stars on Bomoga/repro
Next goal
Next goal
Next goal
Next goal
6,311 contributions in the last year, the three of us combined.
4,680 contributions in the last year by Alexander.
1,368 contributions in the last year by Adrian.
263 contributions in the last year by Brandon.
By primary language of original public repos · data as of September 30, 2026
Repro, the project we built in 36 hours at ShellHacks 2026, won the Microsoft prize. Here is what it is and why we built it the way we did.
Reproduce first, verify after, and a person merges. A walk through the six stages of the Repro pipeline.
Repro spends none of its model tokens finding bugs and an estimated ~68% fewer tokens fixing them. Here is where those two numbers come from.