skills.rest
saleor
saleorOFFICIAL
Explore all skills by this author →
Website𝕏@getsaleorGitHub

analyze-failures

Analyze CI Playwright failure reports to group and triage flaky tests.

1.0k|1.2k|Updated Jun 19, 2019
Search Tags:#Playwright#triage#analyze#failure-analysis#E2E-tests#CI-failures
One-click install
npx skills add https://github.com/saleor/saleor-dashboard --skill analyze-failures
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: analyze-failures
Source: https://github.com/saleor/saleor-dashboard/tree/main/.claude/plugins/dashboard-playwright/skills/analyze-failures
Command: npx skills add https://github.com/saleor/saleor-dashboard --skill analyze-failures

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill analyzes CI Playwright failure reports to identify, group, and triage flaky tests and app bugs, reducing investigation time and improving fix quality.

Core Features & Use Cases

  • Automated failure ingestion: Accepts merged blob reports from CI, GitHub Actions runs, PR URLs, ZIP artifacts, or local folders.
  • Semantic categorization & root-cause hints: Extracts failures, assigns categories and root-cause hints to speed up triage.
  • AI-assisted triage & delegation: Spreads investigations to subagents for deeper analysis and fixes, when needed.
  • Use Case: When a CI run reports multiple failing tests, run this Skill to produce a structured summary and grouping, enabling targeted debugging.

Quick Start

Provide input as a GitHub Actions run URL, PR URL, zip containing merged-blob-reports, or a folder path containing reports, and run the Skill to generate enriched failure summaries ready for review.

Frequently Asked Questions about analyze-failures

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

FAQPage Schema
How do I analyze Playwright E2E test failures from CI runs?▼

You can analyze Playwright E2E test failures by providing a GitHub Actions run URL, PR URL, zip artifacts, or local folder path containing merged blob reports, which the Skill processes to extract and categorize structured failure data.

What is the best way to triage flaky tests and app bugs in Playwright reports?▼

The best way to triage flaky tests and app bugs in Playwright reports is to use AI-assisted triage, which groups failures, assigns root-cause hints, and delegates investigations to subagents for targeted debugging and remediation.

Can I use GitHub Actions run URLs to diagnose CI failures in Playwright?▼

Yes, you can use GitHub Actions run URLs to diagnose CI failures in Playwright, as the Skill accepts these URLs along with PR URLs, ZIP artifacts, or local folders containing merged blob reports as valid inputs for analysis.

How does AI triage work for grouped Playwright failure analysis?▼

AI triage for grouped Playwright failure analysis works by extracting structured failure data from merged reports, assigning semantic categories and root causes, and spreading investigations to subagents to produce enriched summaries suitable for automated triage.

Do I need merged blob reports to identify root causes in Playwright E2E tests?▼

You need merged blob reports from CI runs to identify root causes in Playwright E2E tests, as the Skill requires these reports—provided via GitHub Actions run URLs, PR URLs, zipped artifacts, or local folders—to extract and categorize failures.

Related Skills

Explore More Software Engineering Skills→
addxaiaddxai
42

gitlab-mr

Automate GitLab Merge Request lifecycle with CI fixes and conflict resolution.

Official
Advanced
glowingkittyglowingkitty
43

openmates:fix-tests

Triage failing test runs into root-cause groups and apply targeted fixes.

Community
Intermediate
softmgsoftmg

github-workflow-automation

Automate GitHub Actions workflow generation and CI/CD pipeline management.

Official
Advanced
Pear-CommercePear-Commerce

tech-log-test-failure-watcher

Monitor Slack #tech-log for api.pearcommerce.com test failures and triage them.

Official
Advanced