Review Agent Skill

Review

A finished change earns "done" only after three lenses pass: its shape, its

diff, and its docs. Each has a specialist skill. This skill owns only

what they can't — the order they run in, the loop between them, and one verdict.

Workflow

• Scope. Fix the diff under review and confirm it's substantive; skip the

whole pass for trivial edits.

• Shape — refactor-clean. Run it first, while

restructuring is cheap and before you audit a diff that's about to move.

• Diff — code-review. Audit the settled shape. A

finding that forces a structural change sends you back to step 2, not onward.

• Docs — write-docs. Update the docs this change

touched. Then trace the link chain from the root README down to each one:

every link on the path still resolves, and the hub-to-leaf flow still reads

in order.

• Report. One verdict across all three passes — what each found, what you

changed, what you left and why. Done only when every pass is clean or

resolved.

Rules

• When you enter a pass, read its skill — the rules live there, not here.
• Order governs presentation, not disclosure: surface a finding the moment you

hit it, even when a later pass owns it.

• Loop, don't cascade: a later fix that reopens an earlier pass returns there.

Stop when a full pass adds nothing.