analyze-playwright-traces

Analyze Playwright reports and traces using the playwright-traces-reader CLI commands.

3|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/Kremliovskyi/playwright-traces-reader --skill analyze-playwright-traces-kremliovskyi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analyze-playwright-traces
Source: https://github.com/Kremliovskyi/playwright-traces-reader/tree/main/templates/skills/analyze-playwright-traces
Command: npx skills add https://github.com/Kremliovskyi/playwright-traces-reader --skill analyze-playwright-traces-kremliovskyi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @andrii_kremlovskyi/playwright-traces-reader.

What problem does it solve? Debugging Playwright test failures requires digging through raw trace zips, report folders, and scattered artifacts. This Skill turns that into a structured CLI-driven workflow for locating reports, digesting traces, and extracting failure evidence. ## Core Features & Use Cases - Report Discovery: Search a local playwright-reports hub by metadata, date, or recency with search-reports, then resolve a reportRef into a local path with prepare-report. - Trace Digestion: Use digest to produce a self-contained folder with a chronological step tree, DOM snapshots, network NDJSON, and console logs for token-efficient analysis. - Targeted Inspection: Run summary, network, dom, timeline, console, errors, attachments, and screenshots against a single trace for focused questions. - Use Case: A QA engineer asks to find the latest UAT EU report, locate the failing "checkout" test, and explain why it failed — the Skill searches the hub, prepares the report, finds the trace, digests it, and reads digest.json for the answer. ## Quick Start Ask the AI to find the failing checkout test in the local playwright-report directory and digest its trace for analysis.

Frequently Asked Questions about analyze-playwright-traces

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

FAQPage Schema
How do I analyze a failed Playwright test trace?

Run the digest command with the trace path and an output directory to produce a self-contained folder with digest.json, network.ndjson, console.ndjson, and DOM snapshots. Read digest.json directly for the chronological step tree correlated with network and console events.

How do I find a Playwright report by name or date?

Use search-reports with a metadata query like "UAT EU" plus optional --range-start, --range-end, or --selected-dates filters against the local playwright-reports hub. Then run prepare-report with the returned reportRef to resolve a local analysis-ready path.

Can I find traces for passed or flaky Playwright tests?

Yes, the find-traces command locates traces for any test by name, including passed tests. Use the --outcome flag with values expected, unexpected, flaky, or skipped to filter results, and it returns trace paths for all retries.

Does the DOM snapshot include content inside iframes?

Yes, child iframe and frame content is inlined recursively as srcdoc, producing self-contained HTML with no external snapshot placeholders. The dom command writes JSON to a file via --output, with HTML stored in the snapshots phase fields.

What happens if the playwright-reports hub is not reachable?

The search-reports and prepare-report commands fail with a direct message that the report hub is not reachable at the requested URL. You can pass --base-url or set PLAYWRIGHT_REPORTS_BASE_URL to point at the correct hub address.