e2e-run

Execute Playwright or Cypress tests and generate structured reports with evidence.

Updated Feb 26, 2026

Search Tags:#e2e #reporting #evidence #playwright #cypress #snapshots #test-automation

Ready to run

npx skills add https://github.com/Vamdawn/ai-forge --skill e2e-run

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: e2e-run
Source: https://github.com/Vamdawn/ai-forge/tree/main/skills/e2e-run
Command: npx skills add https://github.com/Vamdawn/ai-forge --skill e2e-run

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the execution of existing end-to-end assets in a project, saving time by capturing execution evidence and producing structured failure analysis with actionable next steps.

Core Features & Use Cases

Discover and route to the correct execution path by locating available e2e scripts (Playwright/Cypress) or Markdown specs.
Execute the chosen e2e assets and save human-readable reports and machine-readable summaries, along with evidence like logs, screenshots, and traces.
Generate concise issue analyses and recommended next steps to help users improve test coverage and reliability.

Quick Start

Run the current project's existing e2e assets, capture execution evidence, and generate a structured problem analysis with next-step recommendations.

Frequently Asked Questions about e2e-run

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

FAQPage Schema

How do I run existing Playwright or Cypress end-to-end tests and capture execution evidence?▼

To run end-to-end tests and capture evidence, this skill automatically discovers your project's Playwright or Cypress assets and executes them. It then isolates snapshot creation to save logs, screenshots, and traces as structured evidence.

Can I validate an e2e spec against a running service without writing new test scripts?▼

Yes, you can validate an e2e spec against a running service. The skill routes execution between available Playwright or Cypress scripts and Markdown specs, validating the spec directly and producing a structured pass or failure report.

What is the best way to generate a structured failure analysis from e2e test results?▼

Generating a structured failure analysis from e2e test results is handled by producing both human-readable reports and machine-readable summaries. The skill analyzes failures and outputs actionable next steps to improve test coverage and reliability.

Does this approach support isolated snapshot creation for Cypress and Playwright test automation?▼

Yes, isolated snapshot creation is supported for Cypress and Playwright test automation. The skill implements asset discovery and route selection, ensuring that snapshots, logs, and traces are captured in isolation during the end-to-end execution.

What mandatory outputs are generated when executing end-to-end tests?▼

Mandatory outputs generated when executing end-to-end tests include a human-readable report, a machine-readable summary, captured service logs, and evidence indexes. These outputs ensure comprehensive documentation of the test run and any failures.