mcaf-dotnet-reportgenerator

MCAF: .NET ReportGenerator

Trigger On

• the repo uses or wants ReportGenerator
• CI needs human-readable coverage reports
• multiple coverage files must be merged

Value

• produce a concrete project delta: code, docs, config, tests, CI, or review artifact
• reduce ambiguity through explicit planning, verification, and final validation skills
• leave reusable project context so future tasks are faster and safer

Do Not Use For

• raw coverage collection with no reporting need

Inputs

• the nearest AGENTS.md
• existing coverage artifacts
• desired output formats

Quick Start

1. Read the nearest AGENTS.md and confirm scope and constraints.
2. Run this skill's Workflow through the Ralph Loop until outcomes are acceptable.
3. Return the Required Result Format with concrete artifacts and verification evidence.

Workflow

1. Keep collection and rendering separate: Coverlet collects, ReportGenerator renders.
2. Prefer the local or manifest-based .NET tool for reproducible CI runs.
3. Choose output formats deliberately:
   • HtmlSummary
   • Cobertura
   • MarkdownSummaryGithub
   • badges
4. Merge multiple reports only when the repo really needs a consolidated view.

Bootstrap When Missing

If ReportGenerator is not configured yet:

1. Detect current state:
   • rg --files -g '.config/dotnet-tools.json'
   • dotnet tool list --local
   • dotnet tool list --global
   • command -v reportgenerator
2. Prefer local tool installation for reproducible CI:
   • dotnet new tool-manifest (if missing)
   • dotnet tool install dotnet-reportgenerator-globaltool
3. Add one explicit render command to AGENTS.md and CI, for example:
   • dotnet tool run reportgenerator -reports:"**/coverage.cobertura.xml" -targetdir:"artifacts/coverage" -reporttypes:"HtmlSummary;Cobertura"
4. Run the report command once and return status: configured or status: improved.
5. If raw coverage outputs are already sufficient and no rendered artifacts are needed, return status: not_applicable.