Bug BlitzOpen the app

How Bug Blitz works

From setting one up to tickets in Linear. Free, no sign-up, nothing to install.

A. In short

  1. 1Set it upList what to test.
  2. 2Share the linkSend it to your team.
  3. 3Everyone testsThirty minutes. Say what broke.
  4. 4Sort it outAgree what matters.
  5. 5Get ticketsClaude puts them in Linear.

B. Who does what, step by step

  1. 1Set up2 min
    YouStart a blitz

    Name the product, link the build, list the flows to walk.

    Bug BlitzMakes the blitz

    An invite link for testers, an admin link for you.

  2. 2Invite1 min
    YouSend the invite link

    Private: only who you send it to. Open: listed for anyone.

    Your testersJoin

    Open the link, add a name. No account.

  3. 3Test30 min
    Your testersWalk the flows

    Thirty minutes on the clock. Say what tripped them up, add a screenshot.

    Bug BlitzOne live board

    Everyone's findings, live, waiting in To sort.

  4. 4Triage15 min
    YouSort and agree

    Plain categories, how bad each one is, dismiss the noise.

  5. 5Tickets5 min
    YouExport to Claude

    Paste the export, check Claude's plan, say yes.

    Claude + LinearFiles them in Linear

    Merges duplicates, tags each with a heuristic, creates and assigns.

  6. 6Next build
    YouFix and run again

    Mark what was sent. Blitz the next build.

    Bug BlitzTidies up

    Deletes it all seven days after the last change.

Set up Claude, once

Claude files the tickets. It needs two things: Linear's connector, so it can reach your workspace, and the Bug Blitz skill, so it knows what to do with an export.

Claude app

  1. 1
    Connect Linear

    In Settings, open Connectors, add Linear and sign in.

  2. 2
    Add the skill

    Download the zip, then upload it as a skill in Settings.

Download the skill

Claude Code

  1. 1
    Connect Linear
    claude mcp add --transport http linear-server https://mcp.linear.app/mcp

    Then run /mcp in a session to sign in.

  2. 2
    Add the skill
    mkdir -p ~/.claude/skills/bug-blitz-tickets && curl -so ~/.claude/skills/bug-blitz-tickets/SKILL.md https://www.urquhart.design/bugblitz/SKILL.md
Read the skill

After a blitz

Press Export on the blitz, paste it into Claude, and ask for the tickets. Claude shows you the plan before it creates anything.

Bug blitz: Fernly, a savings appExported from Bug Blitz · 8 findings

Here's our bug blitz. File the tickets in Linear.

Claude · Bug Blitz skill

Good to know

  • Testers don't need to know UXThey say what happened in their own words and how bad it felt. Sorting into usability heuristics happens at triage, or Claude does it.
  • Private or openPrivate blitzes are reached only through their link. Open ones are listed on the Bug Blitz home for anyone to join. Either way, up to 20 testers: open ones can set fewer.
  • Where things are keptShared blitzes live on the server for seven days after the last change, then go, screenshots included. Your list of blitzes is kept in your browser.
  • No server, still worksWithout a connection a blitz stays on your device, and the export works the same.

Run your first blitz.

Start a blitzSee the example