failure-diagnosis

Diagnose failing Playwright tests through evidence-based triage and root-cause analysis.

7|7|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/civitas-cerebrum/element-interactions --skill failure-diagnosis-civitas-cerebrum
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: failure-diagnosis
Source: https://github.com/civitas-cerebrum/element-interactions/tree/main/skills/failure-diagnosis
Command: npx skills add https://github.com/civitas-cerebrum/element-interactions --skill failure-diagnosis-civitas-cerebrum

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnose failing Playwright tests through structured, evidence-based triage. Many automation failures are ambiguous and waste time; this skill provides a repeatable protocol to collect evidence, reason about causes, and surface actionable fixes.

Core Features & Use Cases

  • Evidence collection: capture error messages, stack traces, failure screenshots, and HTML snapshots.
  • Diagnostic pipeline: stage-by-stage analysis from evidence gathering to root-cause hypothesis and decision making.
  • Autonomous guidance: helps surface fixes or generate precise bug reports for app issues, enabling faster resolution.
  • Use Case: QA automation engineer diagnosing intermittent flakiness across authoring and maintenance modes.

Quick Start

Trigger the failure-diagnosis skill when a test fails to start evidence collection and begin the diagnostic pipeline.

Frequently Asked Questions about failure-diagnosis

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

FAQPage Schema
How do I diagnose failing Playwright tests using evidence-based triage?

Diagnose failing Playwright tests by triggering an evidence-first pipeline that captures error messages, stack traces, screenshots, and DOM snapshots to identify root causes. The skill applies structured triage across authoring, maintenance, and bug-discovery workflows to surface actionable fixes.

What is the best way to find the root cause of intermittent Playwright test flakiness?

Find the root cause of Playwright test flakiness using a diagnostic pipeline that collects failure screenshots and error context, then generates root-cause hypotheses. The structured triage protocol captures HTML snapshots and applies decision rules to reason about ambiguous automation failures.

How does screenshot and DOM inspection help debug Playwright automation failures?

Screenshot and DOM inspection debug Playwright failures by providing concrete visual and structural evidence of the application state at the time of error. The triage pipeline analyzes these artifacts alongside stack traces to form accurate root-cause hypotheses and guide autonomous repair.

Can I automatically generate bug reports from ambiguous Playwright test failures?

Generate precise bug reports from ambiguous Playwright test failures through the skill's autonomous guidance and structured heal/recover protocol. When app issues are detected during triage, the evidence-first pipeline surfaces actionable diagnostic data, enabling faster developer resolution.

Does this failure diagnosis skill work for test maintenance and authoring workflows?

This failure diagnosis skill works across Playwright test authoring, maintenance, and bug-discovery workflows. It applies a repeatable evidence-based protocol to collect artifacts, reason about causes, and surface fixes, making it suitable for diagnosing failures throughout the automation lifecycle.

Why do my Playwright tests fail ambiguously and how do I triage them?

Playwright tests fail ambiguously due to unclear error context, which this skill triages by implementing an evidence-first pipeline with structured error collection and decision rules. It inspects the DOM, reviews failure screenshots, and forms root-cause hypotheses to resolve the ambiguity.