REVIEW, VERIFY AND HAND OFF

Review a UI change by recording it

Reviewing a UI change by reading a diff tells you whether the code is reasonable, not whether the thing is good. The parts that matter, how it feels, what happens on the way in and out, whether the empty case looks finished, only exist when you use it. Record that pass and the feedback carries the evidence with it.

Quick answer

To review a UI change, run the branch, use it the way a user would, and record the pass with Clipy, pointing at anything off and saying whether it blocks, can wait or is fine. Post the link on the pull request. The author watches it, and their AI agent, such as Claude Code, Codex or Cursor, reads it and works through the blocking points first.

Product walkthrough. Tap for sound.

What to record

  1. Run the branch and use it the way a user would.

  2. Hit the states the diff touched, including the boring ones.

  3. Stop and point whenever something is off, and say why.

  4. Say plainly what you would accept: block, fix later, or fine as is.

Say this while you record

Grade each point as you make it. A review where everything sounds equally serious gets treated as equally optional.

The prompt to paste

Replace the link with your own recording's share URL, then paste this into Claude Code, Cursor, Codex, or whichever agent you connected.

Read https://clipy.online/video/<id>

It is a review pass over this branch. Give me a list of the review points I raised, each with the element I was pointing at and the severity I gave it.

Then work through the blocking ones in this repo. Leave the rest as a list at the end so I can decide what goes in this change and what does not.

Separating blocking from optional keeps a review from silently turning into a second feature.

What the agent gets from that link

  • A summary of what happened

    A short written account of the recording, so the agent starts with the shape of the request rather than a wall of raw text.

  • A timestamped transcript

    Your narration with times against it, when audio was captured and processed. This is where your reasoning lives, and it is usually the part that decides whether the agent fixes the right thing.

  • Key moments with frames

    Selected instants from the recording with an image of the screen at that point, so the agent can look at the state you were describing instead of guessing at it.

  • Pointer and click evidence

    Where you clicked and what you were pointing at, with the control's accessibility label when the capture recorded one. It turns "this button" into a specific element.

What changes

Writing it downRecording it instead
Reviewing how it feelsNot possible from a diff.You use it and record the pass.
"This looks off"The author has to guess what you meant.The pointer and the frame say which element.
Blocking versus optionalInferred from tone.Stated, and separated by the prompt.

Tips

  • Connect your agent once

    Run the setup at /agent-setup once. After that every Clipy share link works in the same session you are already in.

  • Say the severity out loud

    The recording cannot infer whether a comment is a blocker or a preference. Grade each one as you go.

  • Review the branch, not your memory of it

    Run the change and use it. A review recorded against the old build is worse than no review.

  • Pick the window you mean

    On a Mac, window capture records only the window you pick, even when other windows cover it. The Mac's window-and-screen-area mode, which includes the camera bubble and Flare, and the Windows app record the window's area of the screen, so close anything you do not want in that area before you start.

Common questions

Should I post the link on the pull request?

That is the usual thing to do. The author watches it and their agent reads it, which means your review gets acted on without being transcribed first.

Does this replace a code review?

No. It covers the half a diff cannot show. Read the code as well.

What if the change is backend only?

Then there is nothing to watch and a written review is the right tool. This is for changes with a visible surface.

Other jobs

The same job, elsewhere on Clipy

This page is the job. These cover the same ground for a specific agent, a specific team, or as a tool you can open right now.

The full list is on the use-case index. If your agent is not connected yet, start at agent setup.