agentleFS
markneoninmarkneonin/paneline/.claude/skills/visual-review/SKILL.md

visual-review

Skill10 starsChanged 19 days agoMITView on GitHub

Use before a paneline task that changes what the pane, status row or chat draws is called done: screenshot every state of the feature, then adversarial visual-reviewer rounds and fixes until a round finds nothing blocking.

14 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 13 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    States: Write visual-review.md with the list of states to shoot: every tab, button and window the change adds or touches, each opened and …

    line 10
  2. Very specific:

    Fix: Every blocking finding with a quote is fixed in the part that draws it, then reshoot every state that part draws.

    line 13

“Common” is measured: kept by at least 6 in 10 of the 13 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Visual review

Record dir: backlog/work/task-<id>/ in the main checkout. Screenshots go to shots/ there (git ignores it).

  1. States. Write visual-review.md with the list of states to shoot: every tab, button and window the change adds or touches, each opened and clicked; empty state; long names; widths 60 and 120 columns; themes dark and light; /color red.
  2. Shoot. Start a session as in skill live-check (own tmux socket, plugin from your worktree, session name main). Per state: drive it with tmux -L <socket> send-keys or python3 .claude/skills/visual-review/click.py <socket> "<label>" [nth], wait for it to settle, then python3 .claude/skills/visual-review/shot.py <socket> <record dir>/shots/r<round>-<state> [light] (pass light for the light themes). That writes .png, .txt and .ansi. Crop nothing.
  3. Review. Dispatch two fresh visual-reviewer agents in one message. Give each only the PNG paths and the ticket's user-visible acceptance criteria. Never the diff, your reasoning or the last round's verdict.
  4. Fix. Every blocking finding with a quote is fixed in the part that draws it, then reshoot every state that part draws. A nit goes to the ticket notes, not into a fix. A finding you think is wrong goes to the owner.
  5. Repeat 3-4 with new reviewers until one round has blocking: 0 from both. After round 5 with blocking findings left, stop and give the owner the list with its PNGs.
  6. Record. Append each round to visual-review.md: findings, what fixed them. Under the last round list the final PNG paths (relative, shots/...), and end the file with the line verdict: clean. A change that draws nothing different ends with verdict: no-ui - <why> instead.
  7. Report. The done report to the owner names the final PNGs.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.