/ skills /qa-checklist
Skill · Claude Code

qa-checklist

The checks only you can run, as a list you tick off

Use it when Claude shipped something it could not fully test itself, on a real phone, with real data or against a service it cannot reach, and you want the checks as a short list you work through rather than instructions that scroll away in chat.

Try it: paste this into Claude Code
Use /proofs:qa-checklist to list the checks I need to run on what you just shipped.
7 features

1What you see

01

Pass, Fail or Couldn't Test

One answer per check

Each check has three answers, including the honest one for a check blocked by an earlier failure.

02

Most Important First

Checks are ordered by what a failure would cost

A crash or lost data comes first, so the checks that matter most get done even if you stop halfway.

03

What Pass Looks Like

Every check says what you should see

Each check names the expected result and why it is on the list, and asks for the exact evidence Claude needs if it fails.

04

Why Claude Couldn't Check It

Each check says what stopped Claude

A check is on your list because Claude could not run it: no real phone, no live data, a service it cannot reach. Each one says which.

05

Not a Bug, Not Built Yet

What will look broken is named up front

If something will look broken but simply isn't built yet, the page says so, so it doesn't come back as a bug report.

06

Results in One Paste

Copy my results sends them all back

One button copies every result and note, with anything you have not reached marked as not checked.

07

Where the Page Goes

A private link, a local file, or your Wi-Fi

Your project picks where review pages go: a private claude.ai link, an HTML file that opens in your browser, or that file served on your home Wi-Fi so a phone can open it. Nothing is ever uploaded or tunneled in the Wi-Fi mode, and the server stops when the review ends.