/ skills /pr-qa
Skill · Claude Code

pr-qa

See what each pull request really changed before you merge it

Use it when Pull requests are waiting, especially ones an AI agent opened while you were away, and you want screenshots and findings instead of reading a diff.

Try it: paste this into Claude Code
Use the pr-qa skill to check every open pull request before I merge anything.
24 featuresDesktop and phone screenshotsNothing merges until you choose

1Before it starts

01

Every Open PR, Every Time

With no arguments, it checks all open pull requests

The list comes from your code host, not from whatever the conversation happened to mention. It says up front which pull requests it is covering, and names any it skipped and why.

02

Nothing Goes Quiet

An opt-in start-of-session note says how many PRs are open

Turn on the optional session reminder with one command and each new session starts with a short note saying how many pull requests are open and how old the oldest one is. It ships with the plugin but stays off until you turn it on with one setting in your project's settings file, and then stays silent when there is no token, no network or nothing open. A pull request nobody mentioned cannot sit unreviewed for days.

2What it checks

03

Runs It for Real

Each branch is checked out, started and used

Every pull request is read first to find the page and the record that show the change, then run for real: checked out, started up, signed in and photographed. Helper scripts pick the pages from a map you write for your own routes, and you bring the screenshot step (the scripts read the before and after evidence you produce). Nothing is recommended for merging that was not actually run.

04

Before Shots Come First

The main branch is photographed before anything changes

Before pictures are taken on the main branch before the pull request runs, so a database change cannot get in the way of capturing the old state.

05

Desktop and Phone, Every PR

Both screen sizes for every pull request

Every pull request is captured at desktop size and at phone size, even a change that seems desktop-only, because phone layouts are where things quietly break.

06

Proof It Signed In

It refuses to save a picture of the sign-in page

Before any screenshot is saved, it checks the page is not the sign-in form and that something unique to the change is on screen. A failed sign-in can look like a normal page load, and four perfect pictures of a login form are not evidence.

07

Real People Stay Private

Names and emails are replaced before the shot

On admin pages, real names and email addresses are overwritten on the page before the screenshot is taken, so nothing personal reaches the shared review page. Cropping afterward is not trusted to do the same job. Your screenshot step is told to do this redaction.

08

Its Own Tests, Counted

Says whether the pull request added any tests

The pull request's own tests are run, and the report says whether it added any. A passing suite and a tested change are not the same claim.

09

What Tests Can’t Catch

A checklist of problems that pass every test

Each pull request is checked for things a green suite misses: two PRs making the same database change, old records missing new data, layouts that wrap badly, private details showing up where they shouldn't, a page left outside a lock, and comments that contradict the code.

10

Honest When It Can’t Reproduce

Says so when the reported bug doesn't happen

If the original bug cannot be made to happen, the report says so instead of calling the change a confirmed fix. It may still be an improvement, but you learn to check it on a real device.

11

No Useless Pictures

Common setup mistakes are ruled out first

Before shooting, it rules out the usual ways a screenshot run goes wrong: missing styles, missing settings, two apps on one port, and a sample record that doesn't show the change. Every picture is looked at before it goes on the page.

3The review page

12

The Verdict Up Top

A summary table you can decide from alone

The page opens with a table of every pull request: its test result and the recommended action. You can stop reading there and still make a decision.

13

Worst First

The one that must not merge sits at the top

Pull requests are ordered worst first, each with a status label, so bad news is never buried under the safe ones.

14

Flip Between Views

Before/After and Desktop/Phone switches on each PR

Each pull request has two switches, Before/After and Desktop/Phone, over a single picture. It opens on the view that shows the change best.

15

Phone at Phone Size

Phone shots are shown at true phone width

Phone screenshots are shown at real phone width and centered, not stretched across the card, where giant text would make them look like desktop shots. They are captured sharp enough to stay crisp at that size.

16

Findings in Plain Words

Numbered findings: what is wrong and why it matters

Each finding is one sentence on what is wrong and one on why it matters. You can act on them, or send them back as the brief for another try.

17

Unchecked Never Looks Clean

A PR nobody reviewed says so plainly

If no reviewer has written findings for a pull request, it reads “not yet read by a reviewer” instead of showing an empty, problem-free list. A gap stays visible as a gap.

18

Tested Before You See It

The review page is checked before it's published

Before publishing, the page is loaded and clicked through automatically: every picture is present, the switches change the picture, phone view stays phone-sized, and the export lists every pull request.

4How you decide

19

Four Clear Choices

Merge and push, merge and hold, send back, or wait

Each pull request gets one decision, with a line under each option saying exactly what will happen. Wait, I will check it myself is always there, because not deciding yet is allowed.

20

A Recommendation, Not a Default

The suggested choice is marked, never pre-selected

The recommended decision carries a badge, but nothing is selected for you. Nobody can approve a merge by scrolling past it, and an untouched pull request exports as no decision yet.

21

One Paste Back

Copy my decisions sends every verdict to Claude

One button copies a plain-text block per pull request, which you paste into chat to have the decisions carried out.

5After you decide

22

Done the Way You Said

Each decision is carried out, one per pull request

Merges are made, held locally or pushed exactly as chosen, with a note when a deploy or database change follows. Sent-back findings become the brief for another attempt, and if that needs you to edit a ticket, it tells you instead of quietly doing the work itself.

23

Leaves No Mess

Your project is put back the way it was

When it is done, test database changes are rolled back, the main branch is checked out again, and temporary working copies are removed, because other sessions may be using the same machine.

24

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.