foryourhealth111-pixel/Vibe-Skills / bundled/skills/generating-test-reports
generating-test-reports
VerifiedGenerate structured test reports with pass/fail rollups, coverage summaries, and test artifacts. Use when the user is asking for test-result packaging or delivery, not for root-cause debugging or feature implementation.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.4 KB |
| assets/README.md | markdown | 285 B |
| assets/example_config.yaml | config | 2.6 KB |
| assets/report_template.html | other | 3.6 KB |
| assets/sample_test_results.json | config | 3.6 KB |
| references/README.md | markdown | 387 B |
| scripts/README.md | markdown | 592 B |
| scripts/aggregate_results.py | script | 2.9 KB |
| scripts/analyze_trends.py | script | 4.7 KB |
| scripts/generate_report.py | script | 3.7 KB |
SKILL.md
View on GitHub---
name: generating-test-reports
description: |
Generate structured test reports with pass/fail rollups, coverage summaries, and test artifacts.
Use when the user is asking for test-result packaging or delivery, not for root-cause debugging or feature implementation.
allowed-tools: Read, Write, Edit, Grep, Glob, Bash(test:report-*)
version: 1.0.0
author: Jeremy Longshore <jeremy@intentsolutions.io>
license: MIT
---
# Test Report Generator
## Purpose
Use this skill when the next deliverable is a readable test report rather than another round of debugging.
## When to Use
Use this skill when:
- Summarizing pass/fail status, flaky tests, or coverage output for others to read
- Turning raw `pytest`, JUnit, or coverage artifacts into a concise report
- Producing release, QA, or review-facing test documentation
## Not For / Boundaries
- Root-cause debugging of a failure: use `systematic-debugging`
- Code review of the underlying implementation: use `code-reviewer`
- Implementing a new test suite from scratch: use `tdd-guide`
## Typical Outputs
- Test execution summary with totals and failure clusters
- Coverage snapshot and quality-gate status
- Follow-up action list for the most important failures
## Related Skills
- `systematic-debugging` before report packaging if failures are still unexplained
- `verification-before-completion` when the report is part of a completion gate
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |