E2E Failure Analyzer

Analyzes Playwright e2e test failures from a GitHub Actions run using JSON reports, trace files, screenshots, and test logs to identify root causes and suggest next actions.

When to Use

• A CI run has failed and you want to understand why
• Triaging e2e test failures from Test: Merge to branch, Test: Full Suite, or Positron Build: Daily Release
• Triaging a whole run's hard failures (for deep per-test investigation of one flaky/failing test, use the triage-e2e-test skill instead)

Prerequisites

• GitHub CLI (gh) authenticated
• @playwright/test available via npx (for merging blob reports, positron repo only)

Helper Scripts

Scripts live alongside this skill in scripts/. Use the base directory path shown above when the skill loads (the "Base directory for this skill: ..." line) as $SKILL_DIR. Scripts require Node.js and are cross-platform (Windows via Git Bash, macOS, Linux). Scripts that extract from zip files require unzip to be available in PATH (included in Git Bash on Windows).