e2e-verify

Automate end-to-end UI verification in a real browser with Playwright, Cypress, or agent-browser.

125|35|Updated Jan 21, 2026

Search Tags:#automation #e2e #qa #playwright #cypress #e2e-testing #browser-testing

Ready to run

npx skills add https://github.com/jh941213/my-cc-harness --skill e2e-verify

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: e2e-verify
Source: https://github.com/jh941213/my-cc-harness/tree/main/skills_en/e2e-verify
Command: npx skills add https://github.com/jh941213/my-cc-harness --skill e2e-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After development + /verify completion, verifies that the implemented feature works in an actual browser via E2E tests.

Core Features & Use Cases

End-to-end validation: simulates real user interactions to confirm features function in a live browser.
Test authoring guidance: provides a framework for creating e2e tests across Playwright, Cypress, or agent-browser based setups.
Use Case: Imagine you have a new feature behind /verify; you want to ensure it flows correctly across pages and components in the browser.

Quick Start

Create or update tests under the e2e/ directory to cover the feature's user flows and run with your preferred framework.

Frequently Asked Questions about e2e-verify

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

FAQPage Schema

How do I automate end-to-end testing for UI features in a real browser?▼

Automated E2E testing validates UI features by simulating real user interactions in a browser. You create tests under the e2e/ directory covering user flows and execute them using frameworks like Playwright or Cypress.

Can I use Cypress or Playwright to validate user flows after a feature is implemented?▼

Yes, you can validate user flows using Cypress or Playwright. The E2E verification process supports these frameworks to simulate real user interactions and confirm features function correctly in a live browser environment.

What do I need to run E2E browser tests on my application?▼

To run E2E browser tests, you need a runnable application, a successful /verify completion for your feature, and access to an e2e testing framework. Tests are placed in the e2e/ directory to cover user flows.

When should I run automated browser tests instead of manual verification?▼

Automated browser tests should run after development and /verify completion to ensure implemented features work across pages and components. They simulate real user interactions to validate flows in a live browser.

Does E2E verification work with agent-browser test suites?▼

Yes, E2E verification supports agent-browser test suites alongside Playwright and Cypress. It automates end-to-end validation of UI features by simulating real user interactions in an actual browser environment.

What is the best way to verify that a new feature flows correctly across pages?▼

The best way to verify cross-page feature flows is through automated E2E tests. By creating tests in the e2e/ directory that simulate real user interactions, you confirm the feature functions correctly in a live browser.