report-buglisted

Turn a failed Playwright run into a ready-to-file bug report draft — repro steps, expected vs actual, correlated runtime observations and evidence paths — for a human to review and file. Never files anything itself.
Diegocortes15/playwright-ia-automation-framework-saucedemo · ★ 0 · Data & Documents · score 63

Install: claude install-skill Diegocortes15/playwright-ia-automation-framework-saucedemo

# report-bug Given the last failed run, this skill assembles a bug report you can paste into a tracker: repro steps, the acceptance criterion the test traces to, expected versus actual, any runtime observations recorded during that test, and the paths to the screenshot, video and trace. **It files nothing.** You invoke it, you read the draft, you decide. That division is the point: the tedious part is transcription, and the part that needs judgment — is this a defect in the application, or a ticket that describes behaviour the application never had? — stays with a person. ## How to use it Run the suite first, then: > Use the report-bug skill. Or for one failure when several failed: > Use the report-bug skill for the test about sorting. ## Workflow The full procedural workflow is in [`references/workflow.md`](references/workflow.md). Read that file before executing the skill. ## References - [`references/workflow.md`](references/workflow.md) — the procedural workflow - [`references/report-template.md`](references/report-template.md) — the draft's structure, and the two-readings rule ## Scripts - [`scripts/collect-failure.mjs`](scripts/collect-failure.mjs) — gathers the failure, its evidence, its acceptance criterion and its observations into structured JSON. Plain Node, no dependencies. Locating facts is lookup, not judgment, so it is a script rather than prose. - [`scripts/collect-evidence.mjs`](scripts/collect-evidence.mjs) — copies that failure's screenshot, vi