Skip to content
Back to skills

Generating Test Reports

ASecurity

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.

  • 3,126 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added May 29, 2026
ai-agentsbashdebuggingcode-reviewdocumentation

Security analysis

A100/100

Pro scans all 10 files and shows the line behind each finding

Scanned May 29, 2026

npx -y skills add foryourhealth111-pixel/Vibe-Skills --skill generating-test-reports --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Generating Test Reports?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Generating Test Reports
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/foryourhealth111-pixel-generating-test-reports/badge)](https://www.skillsdirectory.com/skills/foryourhealth111-pixel-generating-test-reports)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
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

Files in this skill

  • SKILL.md1.4 KB
  • assets/README.md285 B
  • assets/example_config.yaml2.6 KB
  • assets/report_template.html3.6 KB
  • assets/sample_test_results.json3.6 KB
  • references/README.md387 B
  • scripts/README.md592 B
  • scripts/aggregate_results.py2.9 KB
  • scripts/analyze_trends.py4.7 KB
  • scripts/generate_report.py3.7 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…