Agent reviewOutside scope
The role selector disappeared.
This PR changes invitation copy. Owners still need to choose a role before sending an invitation.
team-invitationteam-access.md
Let your agent see the application change.
Run a user journey, capture the screen and compare it with an earlier snapshot. Your agent can check the visible difference against the change you intended.
reflow / Team invitationsIllustrative example
Change Summary
1 changed screenUpdate invitation copy
invite-memberPassed
team-invitation/settings/teamThe test passed. The screen changed.
site.snapshotCapture the screen where behavior matters.
Open a page, fill a form and assert the result before taking a named snapshot. Keep the screenshot with the flow that produced it so the reviewer can inspect the application state.
- Named screenshots
- Step outcomes
- Original before and after captures
Compare the view, then check the scope.
A test can send an invitation successfully while a role selector disappears. Before and after screenshots let your agent point to that change and explain why it needs review.
Your agent can link the original captures in its review, explain the impact on the user and propose another check. A visual difference needs interpretation; it may be exactly what the PR was meant to change.
Bring the evidence into PR reviewA named screen in a browser flow
Select the application URL in your private Browser connection. Relative routes let the flow run against your local app or a reachable preview.
Your agent can inspect the installed plugin’s commands and write the flow using your application knowledge. Select the plugin version in the flow’s requirements.
Flow excerptBrowser
---
providers:
site: Browser
---
site.open url="/settings/team"
site.click selector="[data-testid=invite-member]"
site.expect selector="h2" text="Invite a teammate"
site.snapshot name="team-invitation" selector="[data-testid=invitation-form]"Plugin requirements and private connection settings are configured separately.