skills.rest
parisgroup-ai
parisgroup-aiOFFICIAL
Explore all skills by this author →
GitHub

e2e-analyze

Analyze E2E failures from test results and historical logs into structured diagnoses.

1|2|Updated Apr 6, 2026
Search Tags:#testing#debugging#e2e#analysis#history#code-correlation#timelines
One-click install
npx skills add https://github.com/parisgroup-ai/imersao-ia-setup --skill e2e-analyze
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: e2e-analyze
Source: https://github.com/parisgroup-ai/imersao-ia-setup/tree/main/skills/e2e-analyze
Command: npx skills add https://github.com/parisgroup-ai/imersao-ia-setup --skill e2e-analyze

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze E2E failures by reconstructing failure timelines, associating events with code changes, and looking up historical resolutions to speed debugging and remediation.

Core Features & Use Cases

  • Timeline reconstruction for each failure to visualize the sequence of events.
  • Code correlation to identify mismatches between expected routes or components and actual outcomes.
  • History lookup to detect recurring failures and apply known fixes or workarounds.
  • Output of a structured diagnosis file (e.g., apps/web/e2e-diagnosis.yaml) for automation and traceability.

Quick Start

Run /e2e-analyze after your e2e run to generate a structured failure analysis and suggested fixes.

Frequently Asked Questions about e2e-analyze

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

FAQPage Schema
How do I diagnose E2E test failures using timelines and code correlations?▼

To diagnose E2E test failures, this Skill reconstructs failure timelines, associates events with code changes, and looks up historical resolutions to speed debugging and remediation. It generates a structured diagnosis file for automation and traceability.

What is the best way to analyze recurring E2E failures in web apps?▼

The best way to analyze recurring E2E failures is by using history lookup to detect recurring issues and apply known fixes. This Skill correlates current test outcomes with past resolutions to speed debugging and improve test stability across web apps.

How do I generate a structured diagnosis file from E2E test results?▼

You generate a structured diagnosis file by running the analysis process after your E2E run. It requires access to e2e-run-result.yaml and historical logs to build a comprehensive diagnosis, outputting a file like e2e-diagnosis.yaml.

Do I need historical logs to analyze E2E test failures?▼

Yes, you need historical logs to analyze E2E test failures effectively. The Skill requires access to these logs alongside e2e-run-result.yaml to build a comprehensive diagnosis, detect recurring failures, and apply known fixes or workarounds.

Can I visualize the sequence of events leading to an E2E test failure?▼

Yes, you can visualize the sequence of events leading to an E2E test failure through timeline reconstruction. This feature maps out the failure timeline to help you identify mismatches between expected routes or components and actual outcomes.

How do I identify code mismatches causing E2E test failures?▼

You identify code mismatches causing E2E test failures through code correlation features. This process associates failure events with code changes to pinpoint discrepancies between expected routes or components and actual outcomes, guiding bug fixes.

Related Skills

Explore More Software Engineering Skills→
iamcxaiamcxa
3

e2e-skill-ops

Diagnose e2e skill failures and maintain cross-skill consistency.

Community
Advanced
walter-lawalter-la

dummy-01-intake

Parse unstructured issue descriptions to classify task types and output structured data.

Community
Basic
hepai-labhepai-lab
21

playwright-cli

Automate browser interactions and testing tasks using the Playwright CLI.

Community
Advanced
mkusakamkusaka
7

verify-skill

Verify code changes by manually observing runtime behavior before commit.

Community
Advanced