report
alirezarezvani/claude-skills
Generate test reports with automatic routing to TestRail, Slack, GitHub, or HTML.
What is report?
Generates test reports from Playwright test results and automatically routes them to configured destinations (TestRail, Slack, GitHub Actions, or HTML). Use when you need a test summary, results dashboard, or status overview.
- Parse Playwright JSON test results and extract pass/fail/skip/flaky counts
- Generate markdown reports with failed test details and error messages
- Auto-detect and route reports to TestRail, Slack, GitHub Actions, or HTML viewer
- Compare test trends over time if historical reports exist
- Provide per-browser breakdown (Chromium, Firefox, WebKit)
How to install report
npx skills add https://github.com/alirezarezvani/claude-skills --skill report- Playwright installed and configured
- Test results available (runs tests if none exist)
- Optional: TESTRAIL_URL, SLACK_WEBHOOK_URL, or GitHub Actions environment
How to use report
- 1.Check for existing test results in test-results/ or playwright-report/
- 2.Run tests with JSON reporter if no recent results found
- 3.Parse the JSON report to extract test counts, durations, and failures
- 4.Detect configured destinations (TestRail, Slack, GitHub, HTML)
- 5.Generate markdown report and route to appropriate destination
- 6.Compare with historical reports if available
Use cases
- Post test results to Slack after CI runs
- Generate a markdown test report for documentation or PR comments
- Push results to TestRail for test case tracking
- Display HTML report in browser or CI artifact
- Track test pass rate trends across multiple runs
- QA engineers managing test suites
- CI/CD pipeline maintainers
- Development teams using Playwright for end-to-end testing
- Teams using TestRail or Slack for test reporting
report FAQ
The skill automatically runs Playwright tests with JSON, HTML, and list reporters if no recent results are found.
Yes. It auto-detects all configured destinations (TestRail, Slack, GitHub Actions) and routes accordingly.
Yes, if previous reports exist in test-reports/, it compares pass rates and identifies newly flaky or recurring failures.
It generates a markdown report saved to test-reports/ with full test details, summaries, and per-browser breakdowns.
Yes. It detects GitHub Actions workflows and posts results as PR comments via artifacts, or to Slack/TestRail if configured.
Full instructions (SKILL.md)
Source of truth, from alirezarezvani/claude-skills.
name: "report" description: >- Generate test report. Use when user says "test report", "results summary", "test status", "show results", "test dashboard", or "how did tests go".
Smart Test Reporting
Generate test reports that plug into the user's existing workflow. Zero new tools.
Steps
1. Run Tests (If Not Already Run)
Check if recent test results exist:
ls -la test-results/ playwright-report/ 2>/dev/null
If no recent results, run tests:
npx playwright test --reporter=json,html,list 2>&1 | tee test-output.log
2. Parse Results
Read the JSON report:
npx playwright test --reporter=json 2> /dev/null
Extract:
- Total tests, passed, failed, skipped, flaky
- Duration per test and total
- Failed test names with error messages
- Flaky tests (passed on retry)
3. Detect Report Destination
Check what's configured and route automatically:
| Check | If found | Action |
|---|---|---|
TESTRAIL_URL env var | TestRail configured | Push results via /pw:testrail push |
SLACK_WEBHOOK_URL env var | Slack configured | Post summary to Slack |
.github/workflows/ | GitHub Actions | Results go to PR comment via artifacts |
playwright-report/ | HTML reporter | Open or serve the report |
| None of the above | Default | Generate markdown report |
4. Generate Report
Markdown Report (Always Generated)
# Test Results — {{date}}
## Summary
- ✅ Passed: {{passed}}
- ❌ Failed: {{failed}}
- ⏭️ Skipped: {{skipped}}
- 🔄 Flaky: {{flaky}}
- ⏱️ Duration: {{duration}}
## Failed Tests
| Test | Error | File |
|---|---|---|
| {{name}} | {{error}} | {{file}}:{{line}} |
## Flaky Tests
| Test | Retries | File |
|---|---|---|
| {{name}} | {{retries}} | {{file}} |
## By Project
| Browser | Passed | Failed | Duration |
|---|---|---|---|
| Chromium | X | Y | Zs |
| Firefox | X | Y | Zs |
| WebKit | X | Y | Zs |
Save to test-reports/{{date}}-report.md.
Slack Summary (If Webhook Configured)
curl -X POST "$SLACK_WEBHOOK_URL" \
-H 'Content-Type: application/json' \
-d '{
"text": "🧪 Test Results: ✅ {{passed}} | ❌ {{failed}} | ⏱️ {{duration}}\n{{failed_details}}"
}'
TestRail Push (If Configured)
Invoke /pw:testrail push with the JSON results.
HTML Report
npx playwright show-report
Or if in CI:
echo "HTML report available at: playwright-report/index.html"
5. Trend Analysis (If Historical Data Exists)
If previous reports exist in test-reports/:
- Compare pass rate over time
- Identify tests that became flaky recently
- Highlight new failures vs. recurring failures
Output
- Summary with pass/fail/skip/flaky counts
- Failed test details with error messages
- Report destination confirmation
- Trend comparison (if historical data available)
- Next action recommendation (fix failures or celebrate green)
Related skills
More from alirezarezvani/claude-skills and the wider catalog.

research-summarizer
Structured research summarization agent skill for non-dev users. Handles academic papers, web articles, reports, and documentation. Extracts key findings, generates comparative analyses, and produces properly formatted citations. Use when: user wants to summarize a research paper, compare multiple sources, extract citations from documents, or create structured research briefs. Plugin for Claude Code, Codex, Gemini CLI, and OpenClaw.

resume
Resume a paused experiment, read history, and continue iterating from where you left off.

revenue-operations
Analyzes sales pipeline health, revenue forecasting accuracy, and go-to-market efficiency metrics for SaaS revenue optimization. Use when analyzing sales pipeline coverage, forecasting revenue, evaluating go-to-market performance, reviewing sales metrics, assessing pipeline analysis, tracking forecast accuracy with MAPE, calculating GTM efficiency, or measuring sales efficiency and unit economics for SaaS teams.

review
Systematically audit Playwright tests for anti-patterns, best practices, and coverage gaps.

risk-management-specialist
Medical device risk management specialist implementing ISO 14971 throughout product lifecycle. Provides risk analysis, risk evaluation, risk control, and post-production information analysis. Use when user mentions risk management, ISO 14971, risk analysis, FMEA, fault tree analysis, hazard identification, risk control, risk matrix, benefit-risk analysis, residual risk, risk acceptability, or post-market risk.

run
Run a single experiment iteration: edit, evaluate, keep or discard.