e2e-review

Reviews Playwright and Cypress end-to-end test diffs for requirement proof, selector stability, and CI reliability.

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/hanh-nd/agent-kit --skill e2e-review-hanh-nd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: e2e-review
Source: https://github.com/hanh-nd/agent-kit/tree/main/plugins/agent-kit/.gemini/skills/e2e-review
Command: npx skills add https://github.com/hanh-nd/agent-kit --skill e2e-review-hanh-nd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? End-to-end tests often pass for the wrong reasons, fail for environmental reasons, or cannot be debugged from CI, making them liabilities instead of protection. This Skill reviews E2E test diffs with a strict evidence standard so every test actually proves the user-visible behavior it claims to protect. ## Core Features & Use Cases - Requirement Drift Detection: Verifies that final assertions prove the stated acceptance criterion or regression rather than incidental details, mocks, or page arrival. - Structured Category Sweep: Audits selector contracts, synchronization, isolation, secrets handling, and CI trust as blockers, plus locator quality, data setup, diagnostics, and CI economics as concerns. - Framework-Aware Judgment: Applies real Playwright and Cypress semantics such as auto-waiting locators, command queuing, and isolation defaults to avoid false findings. - Use Case: A teammate opens a PR adding Playwright tests for a checkout flow. Run this review to catch hard sleeps, order-dependent state, and assertions that prove navigation instead of the business outcome before merge. ## Quick Start Review this Playwright test diff for requirement proof, selector stability, synchronization, isolation, and CI reliability using the e2e-review standard.

Frequently Asked Questions about e2e-review

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

FAQPage Schema
How do I review Playwright test diffs before merging?▼

Review Playwright diffs by checking that final assertions prove the stated requirement, selectors use stable roles or test IDs, waits bind to observable conditions, and tests run in isolation. This Skill produces a structured report with blockers, concerns, and nitpicks.

What makes an E2E test flaky in CI?▼

Flakiness comes from hard sleeps, arbitrary timeouts, order dependence, shared mutable state, wall-clock time, and missing service or browser prerequisites. The review flags these as blockers under synchronization, isolation, and CI trust categories.

Does this review work with Cypress as well as Playwright?▼

Yes, the review covers Cypress, Playwright, browser automation, visual regression, and accessibility automation. It applies each runner's real semantics, such as command queuing and retry behavior in Cypress versus auto-waiting locators in Playwright.

When should I use a lower-level test instead of E2E?▼

E2E is justified for critical flows, auth, routing, real rendering, and browser-only regressions. A lower-level test is preferred only when E2E adds little signal relative to its cost, instability, or setup, never merely because one is possible.

Why does the review require a PR description or ticket?▼

Stated intent lets the reviewer check requirement drift, confirming the test proves the actual acceptance criterion. Without intent, only technical E2E quality can be assessed and requirement drift cannot be evaluated.