e2e-verify

Starts a dev stack, authenticates Playwright with the user's browser session, and tests branch changes end-to-end.

21|1|Updated Jul 22, 2026
One-click install
npx skills add https://github.com/uiverify/uiverify --skill e2e-verify-uiverify
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: e2e-verify
Source: https://github.com/uiverify/uiverify/tree/main/packages/skills/skills/e2e-verify
Command: npx skills add https://github.com/uiverify/uiverify --skill e2e-verify-uiverify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually verifying that a branch's changes actually work in a running app is slow and error-prone: you must start the dev stack, log in, click through affected pages, and remember to clean up. This Skill automates that entire loop with Playwright driven by your real browser session. ## Core Features & Use Cases - Isolated dev stack startup: Launches your app on isolated ports so multiple worktrees can run in parallel against a shared database and storage. - Real session authentication: Extracts the session cookie from the user's actual browser (Arc, Brave, Chrome, Edge) and injects it into Playwright, so tests run as a logged-in user. - Diff-aware testing: Analyzes the branch's git diff to map changed files to the UI surfaces that exercise them, then verifies happy paths and edge cases with screenshots. - Use Case: After finishing a feature branch, ask the agent to "e2e verify this branch" — it boots the stack, signs in, exercises the changed flows, persists key assertions into your e2e spec suite, and tears everything down. ## Quick Start Ask the agent to e2e verify the current branch, optionally passing an app URL or port if your stack is already running.

Frequently Asked Questions about e2e-verify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I test my branch changes with Playwright automatically?▼

Invoke the skill with "e2e verify" or "test this branch". It starts your dev stack on an isolated port, authenticates Playwright using your browser's session cookie, analyzes the git diff to find affected surfaces, and exercises them with screenshots.

How does Playwright authentication work with an existing browser session?▼

The skill extracts the session cookie from your logged-in browser (Arc, Brave, Chrome, Edge) via a cookie-extraction command, writes it to a JSON file, then injects the cookies into Playwright's context before navigating. You must already be signed in to the dashboard in your normal browser.

Can I run e2e verification against an already-running app?▼

Yes. Pass an exact app URL (e.g. http://localhost:3020) or just a port number, and the skill skips starting the stack and uses that URL for both authentication and navigation. In that case it also leaves the stack running when finished.

Why does Playwright land on the sign-in page after cookie injection?▼

This means authentication failed, usually because the session token is short-lived and expired. Reload the dashboard in your browser to refresh the token, re-run the cookie extractor for the same exact URL, and never mix localhost with 127.0.0.1 between extraction and navigation.

Where are screenshots and test artifacts stored during verification?▼

All scratch artifacts — screenshots, DOM snapshots, console dumps, and notes — are written under a .e2e-verify directory at the repo root, which is gitignored. The directory is deleted after successful testing but kept if testing fails so you can inspect failures.