OpenParable
Skip to content
← Back to skills

Generating Test Reports

Testing & Quality
generating-test-reports

Generating Test Reports is an Agent Skill for testing & quality published in the foryourhealth111-pixel/Vibe-Skills repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

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.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/foryourhealth111-pixel/Vibe-Skills/blob/HEAD/bundled/skills/generating-test-reports/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/generating-test-reports, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

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