Before and after
Inspect the original screenshots alongside the comparison to decide whether each change was intended.
Give your agent snapshot comparisons to judge which application changes belong in the scope of your PR.
┌────────────┐ ┌────────────┐
│ BEFORE │ │ AFTER │
│ email │ │ email │
│ role [ v ] │ │ │
│ [ invite ] │ │ [ invite ] │
└─────┬──────┘ └──────┬─────┘
└─────────┬────────┘
▼
role selector removed
│
▼
screenshots + PR noteReflow coordinates end-to-end test runs that capture snapshots and compare them. A functional assertion can pass while a control disappears, a label changes, or a layout clips. Your agent inspects the exact before and after evidence against the intended change to determine what is in scope and what needs attention.
A PR meant to update invitation copy also removes the role selector. Your agent flags the unexpected removal, links the snapshots, and explains why it appears outside the intended scope.
Inspect the original screenshots alongside the comparison to decide whether each change was intended.
A snapshot checkpoint without an approved baseline is new. Baseline approval is explicit and separate from merging a pull request.
Your agent can assemble selected captures into a walkthrough for the reviewer.
This example compares the invitation screens and shows the agent’s finding about the missing control.
team-invitation/settings/teamsite.snapshotThis PR changes invitation copy. Owners still need to choose a role before sending an invitation.
Use the setup guide to select plugin versions and configure private connections for your application.
Understand visual comparisonsPR intent: update invitation copy
Changed: team-invitation
Before: invitation included a role selector.
After: the selector is absent.
Impact: the owner cannot choose the new member’s role.
Scope: removing role selection is not part of the copy update.
Review: confirm whether the removal was intentional.
Evidence: original before/after captures.