Bug Blitz, free and open source
Projects412 words
A tool I've built in different versions over time, now released for anyone: run a bug blitz with your team, sort what they find, and let Claude file the tickets.

Bug Blitz is out: a free mini app for running a bug blitz. Your team walks the same core flows on a working build for 30 minutes and says what tripped them up. You sort it, and Claude can file the tickets.
Try it at urquhart.design/bugblitz. The code is on GitHub at DanUrq/bugblitz, MIT licensed.
I've built this tool in different versions over time. This is the first one anyone can use: no sign-up, nothing to install, and the code is open.
How a blitz runs
- Set it up in two minutes. Name the product, link the build, list the flows to walk.
- Share one link. Testers add a first name and they're in. A blitz is private (only who you send the link to) or open (listed for anyone, up to a cap).
- Test. A timer, the flows to tick off, and a note box: what you did, what you expected, what happened. Paste a screenshot if it helps. Everyone sees the same board, live.
- Triage. Findings land in To sort. Each card asks one thing: keep it or dismiss it.
- Tickets. Export the kept findings and give them to Claude with the Bug Blitz skill. It drafts the tickets in Linear, shows you the plan, and creates nothing until you say yes.
Plain words for testers
The people in a blitz are rarely UX people, so nobody has to classify anything. How bad it is gets said in their words: Minor, Annoying, Serious, Blocks me. At triage, findings go into plain categories like "Didn't show what's happening" or "Too easy to get wrong". Each one maps to one of Nielsen's usability heuristics, which is what the export and the tickets use. The rigour is there, out of the way.
What open source changed
Releasing it meant tidying it. Every rule about a finding now lives in one core module that the app and the server share, so they can't disagree. Nobody can change a shared blitz without joining it first. Everything deletes itself seven days after the last change, screenshots included. Upstash's free plan covers the shared boards, and the README says how to deploy your own.
The same code runs on the Bug Blitz page and as an app inside Merlin OS, on the computer in the room.
I built it the way I build everything now: designed first, then built with AI-assisted coding. The guide has the whole flow and the Claude skill to download.