e2e

Classify Playwright and Vitest end-to-end test failures as flaky, outdated, bug, or unverified.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/awfixers-stuff/opencode-config --skill e2e-awfixers-stuff
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: e2e
Source: https://github.com/awfixers-stuff/opencode-config/tree/main/skills/e2e
Command: npx skills add https://github.com/awfixers-stuff/opencode-config --skill e2e-awfixers-stuff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineers quickly diagnose, categorize, and remediate end-to-end test failures so teams can restore reliable CI confidence without making unauthorized changes to application behavior or APIs.

Core Features & Use Cases

  • Failure Taxonomy: Classify failures as flaky, outdated, bug, or unverified to drive the correct remediation path.
  • Prescriptive Fix Rules: Recommend non-invasive fixes for flakiness (better waits, resilient selectors), guidance to update stale tests, and strict rules for bug fixes that require spec citation and unit tests.
  • Workflow Guidance: Discover test configuration, run tests, parse failures, prioritize flaky fixes first, then outdated, then bugs, and produce a reproducible remediation report.
  • Use Case: Triage a failing Playwright suite in CI, identify intermittent timeouts as flaky, update selectors for a redesigned header as outdated, and prepare a spec-backed bug fix with unit tests for validation.

Quick Start

Run the e2e skill to analyze failing end-to-end tests, classify each failure as flaky, outdated, bug, or unverified, and produce prioritized, non-invasive fix recommendations while enforcing spec-backed code changes when required.

Frequently Asked Questions about e2e

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

FAQPage Schema
How do I triage flaky end-to-end test failures in Playwright?▼

To triage flaky end-to-end test failures in Playwright, you can analyze test runs to classify failures as flaky, outdated, bug, or unverified, prioritizing non-invasive fixes like resilient selectors and improved waits to stabilize the suite.

What is the best way to fix intermittent Vitest e2e timeouts during CI?▼

Fixing intermittent Vitest e2e timeouts involves classifying the failures as flaky and applying non-invasive remediation rules, such as recommending better waiting strategies and resilient selectors to restore reliable CI confidence.

How do I categorize outdated e2e tests after a UI redesign?▼

To categorize outdated e2e tests after a UI redesign, parse the failing suite to identify stale tests, update the outdated selectors to match the new DOM structure, and verify the remediation through a reproducible report.

Does this approach require unit tests for bug fixes found during e2e triage?▼

Yes, this approach requires spec-backed code changes for bug fixes found during e2e triage, enforcing strict rules that mandate accompanying unit tests to validate the application behavior and prevent future regressions.

Why should I apply non-invasive fixes first when debugging e2e test failures?▼

You should apply non-invasive fixes first when debugging e2e test failures to stabilize flaky tests without making unauthorized changes to application behavior, prioritizing selector and waiting improvements before addressing outdated tests or underlying bugs.