Boost Test Report Writing Efficiency by 90% with the test-report-writer Skill

Writing test reports at the end of each iteration traditionally requires manually exporting bug lists and test case results, calculating pass rates, identifying open bugs, and assembling risk assessments—a process that often takes more than an hour and is prone to missing critical information.

The test-report-writer skill simplifies this by accepting the exported test execution data and bug data, automatically parsing fields, computing eight key metrics (such as pass rate, closure rate, defect density), and generating a complete, professional report ready for submission.

The generated report follows a fixed eight‑module structure:

Basic Information (project, version, test cycle, environment, scope)

Test Overview (summary and key metrics)

Test Scope (covered and uncovered modules, requirement coverage)

Test Execution Statistics (module‑wise pass rate, lists of failed, blocked, and unexecuted cases)

Defect Analysis (severity, module, owner distribution, P0/P1 details, residual bugs)

Risk Assessment (high/medium priority issues, rollback strategy, mitigation plans)

Conclusion & Recommendations (Go/No‑Go decision, required actions, release checklist)

Appendix (detailed case list, bug list, related document links)

Three report types are available: a full 8‑module summary report, a standard 6‑module report, and a concise version containing only basic statistics and conclusions.

The skill addresses four common problems:

Data consolidation time: manual effort of at least 30 minutes is reduced to a few seconds of upload and automatic calculation.

Inconsistent report structure: the fixed eight‑module format guarantees completeness.

Missing key information: the skill proactively asks for failure reasons, residual bug impact, and rollback plans, ensuring no critical details are omitted.

Time‑consuming presentation: an embedded HTML script converts Markdown to a dark‑theme visual page with metric cards, ready for screenshot or projection. Practical demonstration (AIO platform v2.3) :

Step 1 – Prepare data

Export two files from the bug‑management platform: 45 test case results (including module, title, status) and 61 bug records (title, priority, status, owner, module).

Step 2 – Upload and trigger

In WorkBuddy, upload the files and issue the prompt “Help me write a test summary report for AIO platform v2.3”. The skill detects 6 failed cases, 1 blocked case, and 4 unexecuted cases, then asks follow‑up questions about environment, failure reasons, dependencies, and release risk.

Step 3 – Report output

After five minutes the skill returns a Markdown report containing key metrics such as:

Pass rate: 75.6 % (34/45)

Failed cases: 6 (with reasons and linked bugs)

Blocked cases: 1 (dependency on ops configuration, expected fix 5/30)

Unexecuted cases: 4 (with reasons and retest plans)

Total bugs: 61 (39 fixed, 22 open, 1 P0 fixed pending verification)

Step 4 – HTML visualization

Run the built‑in script to convert the Markdown to an HTML page:

python scripts/report_to_html.py report.md report.html

The resulting dark‑theme page displays six metric cards at the top, auto‑styled tables, and can be directly screenshot or projected. Suitable scenarios include iteration wrap‑up reporting, regression verification, pre‑release acceptance, and multi‑project quality comparison. Limitations : the skill handles data organization and report structuring but does not make technical judgments about bug impact; final release decisions still require human evaluation. How to use :

Within WorkBuddy (recommended): export data, upload, issue a natural‑language request, answer the skill’s follow‑up questions, and retrieve the Markdown or HTML report.

With any AI tool: copy the provided Prompt template into Claude, ChatGPT, DeepSeek, Cursor, etc., and paste the test data.

Overall, the test-report-writer skill reduces manual data‑gathering time from over an hour to five minutes, standardizes report format, and ensures critical information is not omitted, allowing teams to focus on analysis and decision‑making.