reportgenerator

Convert .NET coverage files into HTML, Markdown, Cobertura, and badge reports.

Updated May 2, 2026
One-click install
npx skills add https://github.com/hdeshev/pi-config --skill reportgenerator-hdeshev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reportgenerator
Source: https://github.com/hdeshev/pi-config/tree/main/agent/skills/reportgenerator
Command: npx skills add https://github.com/hdeshev/pi-config --skill reportgenerator-hdeshev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Raw .NET coverage outputs like Cobertura or OpenCover XML are hard to read and share. This Skill turns them into human-readable HTML pages, Markdown summaries, badges, and merged reports that developers and CI pipelines can consume directly. ## Core Features & Use Cases - Multi-format rendering: Generate HtmlSummary, Cobertura, MarkdownSummaryGithub, badges, and more from existing coverage files. - Report merging: Combine multiple coverage files into a single consolidated report when a repo produces several outputs. - CI integration: Add reproducible report commands to pipelines using a local .NET tool manifest, including GitHub step summaries and README badges. - Use Case: A team runs Coverlet in CI and wants a coverage summary posted to each pull request plus an HTML artifact; this Skill configures ReportGenerator to render MarkdownSummaryGithub and HtmlSummary from the collected Cobertura files. ## Quick Start Ask the agent to render the repository's existing coverage.cobertura.xml files into an HTML summary and GitHub Markdown report under artifacts/coverage using ReportGenerator.

Frequently Asked Questions about reportgenerator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate an HTML coverage report from Cobertura XML?▼

Run ReportGenerator with -reports pointing to your coverage.cobertura.xml files, -targetdir for the output folder, and -reporttypes set to HtmlSummary or Html. As a local tool, invoke it with dotnet tool run reportgenerator.

How to merge multiple .NET coverage files into one report?▼

Pass a glob pattern or semicolon-separated list to -reports, such as "**/coverage.*.xml", and set -reporttypes to Cobertura. ReportGenerator merges all matching inputs into a single consolidated output file.

What output formats does ReportGenerator support?▼

ReportGenerator supports HTML variants, Markdown summaries including GitHub-flavored, machine-readable formats like Cobertura, OpenCover, lcov, and SonarQube, plus SVG badges, JSON, CSV, and plain text summaries.

Should I install ReportGenerator globally or as a local .NET tool?▼

Prefer a local tool manifest for reproducible CI runs: create it with dotnet new tool-manifest, then install dotnet-reportgenerator-globaltool. Global installation works for ad-hoc local use but is less reproducible across agents.

When should I not use ReportGenerator?▼

Skip it when raw coverage files already satisfy your needs and no human-readable or merged output is required. It renders reports from existing coverage data; it does not collect coverage itself.

How do I add a coverage summary to GitHub Actions?▼

Generate the MarkdownSummaryGithub format, then append the produced SummaryGithub.md file to $GITHUB_STEP_SUMMARY in your workflow step. Add Badges to the report types if you also want README coverage badges.