playwright-trace-analyzer

Solid

Analyzes Playwright E2E `trace.zip` archives (and bare trace JSONL when unpacked). Extracts the action timeline, network waterfall, console errors, and DOM-snapshot anchors, then identifies the highest-impact problems (flaky waits, slow selectors, network bottlenecks, hung actions, unhandled console errors, navigation churn) and proposes concrete test or app fixes ranked by measured impact. Auto-detects whether the input is a `trace.zip`, a directory of unpacked trace files, or a single `trace.trace` / `trace.network` JSONL stream. Iterates via the `/confidence` skill — if root-cause certainty is below 90%, it digs deeper before recommending a fix. Use when handed a Playwright trace, asked "why is this test flaky?", "why did the test time out?", or asked to optimise an E2E suite with evidence. Triggers on "analyze trace", "playwright trace", "e2e trace", "test flake", "why did playwright fail", "playwright timing", "/playwright-trace-analyzer".

Testing & QA 8 stars 2 forks Updated 2 days ago MIT

Install

View on GitHub

Quality Score: 84/100

Stars 20%

Recency 20%

100

Frontmatter 20%

Documentation 15%

100

Issue Health 10%

License 10%

100

Description 5%

100

Skill Content

# Playwright Trace Analyzer Turn a Playwright `trace.zip` into a ranked, evidence-backed report of flakes, slow steps, and root causes. > **Index file.** Detailed extraction rules, analysis playbooks, and > report templates live under `rules/`, `references/`, and `templates/`. > Load only what the current phase needs — the body of `SKILL.md` is a > thin orchestrator. --- ## Inputs The user passes one or more of: | Input | Detection signal | | ------------------------------------ | ---------------------------------------------------------------------- | | GitHub Actions run URL | Matches `https://github.com/<owner>/<repo>/actions/runs/<id>` — fetch artifacts via `gh run download` | | `trace.zip` archive | Magic bytes `50 4b 03 04`; entries include `trace.trace`, `trace.network`, `*.png`, `resources/` | | Unpacked trace directory | Contains `trace.trace` + `trace.network` (NDJSON) and a `resources/` subdir | | Single `trace.trace` JSONL stream | NDJSON; each line has `type`, `callId`, `startTime`, `params` (e.g. `before`, `action`, `after`) | | Single `trace.network` JSONL stream | NDJSON; entries with `type: "resource-snapshot"` or `requestEvent` / `responseEvent` | | `report.json` (Playwright reporter) | Top-level `config`, `suites`, `stats`; complementary, never authoritative for timing ...

Details

Author: mthines
Repository: mthines/agent-skills
Created: 3 months ago
Last Updated: 2 days ago
Language: TypeScript
License: MIT

Integrates with

GitHub · DevTools Playwright · Testing

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

playwright-trace

Inspect Playwright trace files from the command line — list actions, view requests, console, errors, snapshots and screenshots.

25 Updated 4 days ago

EVEDensity

Testing & QA Solid

playwright-debugger

Use when a Playwright end-to-end test has already run and failed and the user wants the root cause and a concrete fix. Trigger on a failing Playwright spec, TimeoutError, broken or ambiguous selector, post-deploy suite failure, retry-only flake, hydration or timing race, or a passes-locally-but-fails-in-CI split. Accept error messages, playwright-report/ or HTML reports, trace.zip, screenshots, and CI artifacts identified by a GitHub owner/repo slug plus run id. Distinguish product regressions from brittle tests. Do not use for writing new Playwright tests, speeding up or reviewing a passing suite, non-Playwright failures (Cypress, Jest, Vitest), or debugging an app/backend without a failing Playwright test.

9 Updated 5 days ago

voidmatcha

AI & Automation Featured

analyze-performance-traces

Analyze Chrome, Chromium, Electron, React DevTools, or Perfetto-compatible JSON traces and audit user-reported profiling findings without loading large artifacts into context; prove trigger-to-render/layout chains, separate measured facts from source inference, find exact code choke points, classify forced layout and render fanout, implement semantically safe fixes, and verify behavior plus repository budgets. Use for trace files, reported profiling durations or call chains, dropped frames, long tasks, resize or scroll jank, render storms, layout thrashing, selector hot paths, interaction latency, or requests to locate exact source-level bottlenecks.

3,318 Updated today

tutti-os