Who it is forA QA or frontend developer who has a failing Playwright test and needs a clear bug report for the team.
The problemA failing test trace is hard for others to follow, and writing up the steps takes time away from the fix.
The outcomeA narrated film of the steps and the failure, with a Markdown summary ready for an issue, and typed values never shown.
What you need first
- uv installed
- Node.js 24 or 22 LTS (20 or newer works)
- A supported coding agent such as Claude Code, Codex, Cursor, Devin or OpenCode
- About 0.5 to 0.75 GB to download and 1.4 to 1.8 GB in ~/.showtime once installed
- A normal terminal for setup if the agent sandbox blocks the download
Steps
- Install Showtime with the Claude Code plugin commands or the route in the README.
- Make sure the failing test has a Playwright trace available.
- Run
showtime reproon that trace. - Attach the generated film and Markdown summary to your issue after review.
Prompt for your agent
Using the showtime skill in the FavioVazquez/showtime repository, run `showtime repro` on the Playwright trace for <failing test>. Expect a narrated film and a Markdown summary in showtime-out/. Verify that no typed values appear in the film or the summary.
Caveat. The README says repro turns a Playwright trace, so a failing test without a trace cannot be used with this route.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page