report

This skill generates test reports for Playwright test suites and plugs them into whatever workflow a team already uses, without introducing new tooling. It solves the common problem of raw test output being hard to read and easy to lose: instead of leaving a wall of console text, it turns Playwright results into a clear pass/fail/skip/flaky summary with failed-test details, error messages, and per-browser breakdowns.

The workflow first checks for recent results in `test-results/` or `playwright-report/` and runs `npx playwright test` with JSON, HTML, and list reporters if none exist. It then parses the JSON output to extract counts, durations, failed test names, and flaky tests that passed on retry. A routing step inspects the environment and configuration to decide where the report should go: TestRail if a `TESTRAIL_URL` is set, a Slack summary if a `SLACK_WEBHOOK_URL` webhook is configured, PR comments via artifacts under GitHub Actions, or a served HTML report. A markdown report is always produced and saved under `test-reports/`, and if historical reports exist it performs simple trend analysis comparing pass rates and highlighting newly flaky or recurring failures.

The target users are QA engineers, test automation developers, and full-stack teams already using Playwright who want a lightweight, repeatable way to summarize and distribute test outcomes. Typical use cases include end-of-run status summaries, posting results to Slack, and tracking flakiness over time.