e2e-rca

Automate failure detection, categorization, and root cause analysis of Playwright end-to-end tests.

3|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/rlagycks/oh-my-forge --skill e2e-rca
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e-rca
Source: https://github.com/rlagycks/oh-my-forge/tree/main/skills/e2e-rca
Command: npx skills add https://github.com/rlagycks/oh-my-forge --skill e2e-rca

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the detection, categorization, and root cause analysis of failures in web application end-to-end testing, reducing manual debug time and improving test reliability.

Core Features & Use Cases

  • Failure Collection and Categorization: Runs comprehensive Playwright tests to identify and classify various failure types such as selector issues, network errors, and assertion failures.
  • Fault Isolation and Ownership Identification: Differentiates bugs between frontend and backend origins by analyzing API traffic and response patterns.
  • Detailed Root Cause Reporting: Provides structured insights into each failure, including trace analysis, code search, and root cause hypotheses.
  • Use Case: When a complex web app exhibits intermittent UI errors and flaky API responses, this Skill systematically pinpoints whether the problem stems from frontend misconfigurations or backend API inconsistencies, guiding targeted fixes.

Quick Start

Run the Skill to analyze your application's test failures, review the detailed root cause reports, and identify precise points of failure for targeted fixes.

Frequently Asked Questions about e2e-rca

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

FAQPage Schema
How do I automate root cause analysis for Playwright end-to-end test failures?

You can automate root cause analysis for Playwright test failures by running this Skill to detect, categorize, and isolate failures across frontend and backend components, generating structured reports for efficient debugging.

What is the best way to categorize web app test failures and identify frontend versus backend ownership?

Categorizing web app test failures and identifying ownership involves analyzing API traffic and response patterns to differentiate frontend selector issues from backend API inconsistencies, providing structured insights into each failure's origin.

Can I debug intermittent UI errors and flaky API responses without manual trace analysis?

Debugging intermittent UI errors and flaky API responses without manual trace analysis is possible by systematically pinpointing whether problems stem from frontend misconfigurations or backend API inconsistencies, guiding targeted fixes through automated failure collection.

How do I get structured reports for end-to-end test failure categorization and fault isolation?

To get structured reports for end-to-end test failure categorization and fault isolation, the Skill analyzes trace data, performs code search, and formulates root cause hypotheses, detailing precise points of failure for targeted fixes.

Does this root cause analysis approach work for classifying selector issues, network errors, and assertion failures?

Yes, this root cause analysis approach works for classifying selector issues, network errors, and assertion failures by running comprehensive Playwright tests to identify and categorize various failure types across the web application stack.