playwright-trace

What problem does it solve? Debugging failed Playwright tests usually requires opening a graphical trace viewer, which is slow and impractical in headless or CI environments. This Skill lets you inspect .zip trace files entirely from the command line to find exactly what went wrong. ## Core Features & Use Cases - Action Inspection: List all test actions as a tree, filter by title or errors, and drill into any action's parameters, logs, and source location. - Cross-Cutting Views: Review network requests, console messages, and errors across the whole trace with filters for failed requests or error-only output. - DOM Snapshots: Load the DOM snapshot for any action into a headless browser to run eval queries or capture screenshots of the page state at failure time. - Use Case: A CI test run fails overnight. Open the trace, list failed actions, inspect the failing action's snapshot, query the DOM for the error message text, and check for failed network requests — all without leaving the terminal. ## Quick Start Open the trace.zip file from my failed Playwright test and show me which action failed and what the page looked like at that moment.