e2e-bugfix

Diagnose and fix Playwright and Cypress end-to-end test failures.

2|Updated Nov 26, 2025

Search Tags:#debugging #e2e #trace #playwright #cypress #test-failures

Ready to run

npx skills add https://github.com/penkzhou/swiss-army-knife-plugin --skill e2e-bugfix

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: e2e-bugfix
Source: https://github.com/penkzhou/swiss-army-knife-plugin/tree/main/swiss-army-knife/skills/e2e-bugfix
Command: npx skills add https://github.com/penkzhou/swiss-army-knife-plugin --skill e2e-bugfix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a comprehensive framework to diagnose, classify, and fix end-to-end test failures (Playwright, Cypress) by delivering a structured bugfix workflow, error taxonomy, and debugging techniques to accelerate resolution and improve stability.

Core Features & Use Cases

Error classification for common E2E failures (timeouts, locator issues, network errors, flakiness) with guidance on when and how to apply fixes.
Confidence-scoring system to guide triage and decision-making during debugging.
End-to-end debugging techniques including trace analysis, UI mode, screenshots, and best-practice configurations.
TDD-inspired workflow phases (RED, GREEN, REFACTOR) and Page Object patterns to organize tests and reduce regressions.

Quick Start

Describe a complete E2E bugfix workflow for diagnosing and resolving Playwright or Cypress test failures.

Frequently Asked Questions about e2e-bugfix

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

FAQPage Schema

How do I debug flaky Playwright tests in a CI/CD pipeline?▼

Resolve Cypress network errors by classifying them via an error taxonomy, then applying confidence-scoring to guide triage and trace-based diagnostics. This structured workflow isolates network issues and recommends specific configurations to stabilize your test suite.

What is the best way to fix Playwright timeout and locator issues?▼

Fix E2E test timeouts and locator issues by following a structured bugfix workflow that provides explicit error categories, confidence scoring, and recommended commands. This deterministic process helps systematically diagnose and resolve element location failures.

How do I structure a bugfix workflow for failing E2E tests?▼

Structure an E2E bugfix workflow using TDD-inspired phases (RED, GREEN, REFACTOR) combined with Page Object patterns to organize tests and reduce regressions. This framework accelerates resolution by applying error classification and confidence scoring during debugging.

Why are my Cypress tests failing intermittently and how do I score debugging confidence?▼

Intermittent Cypress test failures are classified as flaky tests, and you can score debugging confidence using a dedicated system to guide triage and decision-making. This scoring system helps prioritize which trace-based diagnostics and fixes to apply first.

Does this E2E debugging workflow support both Playwright and Cypress test suites?▼

Yes, the E2E debugging workflow supports both Playwright and Cypress test suites by delivering a comprehensive framework to diagnose, classify, and fix test failures. It applies a deterministic workflow with explicit error categories across modern E2E environments.