/ skills /review-cycle
Skill · Claude Code

review-cycle

Report bugs and ideas as they come; each is fixed, reviewed or saved for later.

Use it when You have a pile of small bugs or requests to report one at a time, often from your phone, and want each one built and merged without being asked questions mid-stream.

Try it: paste this into Claude Code
Start a review cycle. First item: the header overlaps the logo on my phone.
25 featuresEach fix ships as its own pull requestEvery fix shown before and after

1Starting a session

01

Hand It Over, Walk Away

Send reports one at a time or in a batch

Every message after you open the session is treated as a new item in the queue. Anything you send while an item is in progress waits its turn, so new reports never derail half-finished work.

02

Screenshots On by Default

One line tells you screenshots are on; you can opt out

The session starts capturing screenshots of every visible fix without asking you a question first. A single line says so, and one reply turns them off for the rest of the session.

03

A Live Page From Item One

A tracking page goes up before the first fix ships

As soon as the first items arrive, a review page is published with one card per item. The same page is updated after every item, so you can follow along at one link instead of waiting for a summary at the end.

04

The Before, Caught in Time

Claude takes its own before shot when an item comes in

The before screenshot is captured the moment an item arrives, before any code changes, at both phone and desktop size. Once the fix is in, the old state is gone, so every item you review has something real to compare against.

2While it works

05

No “Go” Needed

Moves to the next item on its own, every time

When one item is done, the next one starts in the same turn. You never have to type continue, and a long turn is not treated as a reason to stop. It only pauses when the queue is empty, everything left is waiting on you, or something destructive needs your OK.

06

Test First, Every Fix

Each fix starts with a failing test

Every change is built test-first, the test suite is run until it is green, and the diff is reviewed before it is committed. A fast loop does not mean a sloppy one.

07

One Fix, One Pull Request

Every item gets its own pull request, merged as it goes

Each fix lands on its own branch, cut fresh from the main branch, and its pull request is opened and merged in the same turn. Two items share a pull request only when they touch the same code, so any single fix can be found, reviewed or undone on its own. If your project requires a human review on every pull request, say so at the start and the fixes land as open pull requests instead.

08

Every Request Finds Its Lane

Each item is triaged before anything is built

Small bugs and big feature ideas can arrive in the same stream. Each one is sorted into a lane first: a fix to build now, a design call, a page that looks wrong, a copy edit, a photo, a style rule, a feature to save for later, or a question only you can answer.

09

Design Reviews Start Themselves

A taste call gets its own design review, unasked

When an item has more than one good answer, the design-review skill runs for it on its own: a before screenshot, real mockups, a page to pick from. A page that looks wrong gets visual-qa, copy gets article-copy-edit, a missing picture gets photo-picker. You never have to ask for one, and the queue keeps moving while you decide.

10

Big Ideas Become To-dos

A real feature is saved, not half-built

A request that needs its own plan is saved to your to-do list in your words, with a one-line scope and its open questions, instead of being started inside a session of quick fixes.

11

Hard Bugs Still Get Fixed

A tricky bug is debugged, not handed back

Being hard to track down is not a reason to flag a bug. It gets investigated and fixed without you, and only a specific fact or decision that only you have is saved as a question.

12

A Line Per Item

A short progress line after every item

After each item you get one line: what it was, whether it shipped, went to a design review, was saved as a to-do or was flagged, and how many are left. It is there for you to glance at and needs no reply.

13

Everything Written Down

Every item lands in your to-do file

Each item gets an entry in the project's to-do file with what was asked, why it happened, the approach and any assumption made in place of asking. Shipped items are checked off, so nothing ships silently.

3The tracking page

14

Redirect It Before It’s Built

Every card has a status and a note box

Each card shows where it stands: Reported, In progress, Shipped, In design review, Saved as a to-do or Flagged. A note box is there from the start, so you can add detail, change the request or drop it before any work begins.

15

Opens on What Needs You

Filter buttons with counts, starting on Needs you

Filters for Needs you, Being built, Merged and All show live counts, and the page opens on the items that need you. A banner says plainly whether anything is waiting, including when nothing is.

16

Easy on a Phone

A bar that stays at the top and short pages

A bar stays at the top as you scroll, and cards come about five to a page with a page counter. Even after twenty items, the one that needs you is a tap or two away.

17

Phone and Desktop, Matched

Before and after at the same width, with a switch

After shots are taken at both phone and desktop size, and a Mobile/Desktop switch shows one matched pair at a time, phone first. A phone before is never paired with a desktop after, which would make the change look different than it is.

4At the end

18

Questions Saved for the End

Solo work first, then your questions in one batch

Everything that can be finished without you is done first. Then all the questions are asked together, so you get one round of decisions instead of an interruption per item.

19

Your Verdict on Each Fix

Four answers per shipped item, none pre-selected

Each shipped card offers Looks right, Comment, Request revision and Revert it. Nothing is picked for you, so a fix you never looked at reads as not yet reviewed rather than approved.

20

One Paste Back

Copy my decisions gathers every card's answer

One button copies every decision and note, from any card in any state, as plain text you paste into chat. A note on a reported item changes the request; a revision on a shipped one becomes a new item.

21

Every Flag Has a Next Step

Flagged items say where they go from here

Each flagged item lists why it was held back and the next step, such as a design review, a planning session or simply your decision. A chat recap lists what shipped, what was flagged and anything left half done.

5Long sessions

22

Save Points

Long sessions save their progress between items

A long session saves its progress at an item boundary when a big item finishes and the next is unrelated, after five shipped items, when its memory is half used, or before a clearly large item. Nothing is ever saved mid-item.

23

Nothing Lost at a Save Point

Facts checked, everything filed, nothing left in chat

Before saving, it confirms every merge really landed and the tests pass. The handoff note lists the whole queue, what is merged, what is still open, decisions made, and anything you said that nobody has acted on yet.

24

Keeps Going Afterward

One line, then straight on to the next item

A save point is announced in one line and the next item starts right away; you are never asked to restart the session. If you do clear it, the next session picks up from the handoff note without re-reading old work.

25

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.