How do I install the Coverage Report skill?

Run npx skillmds@latest add nikiforovall/coverage-report in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Coverage Report safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Coverage Report?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Coverage Report free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Coverage Report?

NikiforovAll (@nikiforovall) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Coverage Report by nikiforovall — Agent Skill

Name: Coverage Report
Rating: 4.2 (5 reviews)
Author: NikiforovAll

File contents

Code Coverage Report

Generate a code coverage report scoped to source files changed in the current branch compared to a base branch.

Workflow

1. Determine base branch

Detect the base branch to diff against. Use the MR/PR target branch if known, otherwise default to main or master (whichever exists). Ask the user if ambiguous.

git merge-base --fork-point main HEAD || git merge-base --fork-point master HEAD

2. Detect changed source files

git diff <base-branch> --name-only -- '*.cs'

Filter out test files (paths containing Test, Tests, .Tests, .Test). If no source files changed, stop and inform the user.

3. Identify test project(s)

Determine which test project(s) to run. Strategies (in order):

User-specified: If the user names a test project, use it
Convention-based: Look for test projects whose name matches the changed project (e.g., MyProject -> MyProject.Tests)
Solution-wide: Run all tests in the solution if scope is unclear
Ask: If ambiguous, ask the user which test project(s) to run

4. Clean previous results

rm -rf TestResults/

5. Run tests with coverage

dotnet test <test-project-or-solution> \
  --collect:"XPlat Code Coverage" \
  --results-directory ./TestResults/

6. Build file filters

From the changed file list (step 2), extract basenames and build a filter string:

+*FileName1.cs;+*FileName2.cs;+*FileName3.cs

7. Generate report

dotnet reportgenerator \
  -reports:"TestResults/**/coverage.cobertura.xml" \
  -targetdir:"TestResults/CoverageReport" \
  -reporttypes:"Html;TextSummary" \
  -filefilters:"<filters>"

8. Display results

Print TestResults/CoverageReport/Summary.txt to the terminal
Open the HTML report (platform-aware):
- Windows: start TestResults/CoverageReport/index.html
- macOS: open TestResults/CoverageReport/index.html
- Linux: xdg-open TestResults/CoverageReport/index.html

Tips

For large solutions, scope to specific test projects to speed up collection
The -filefilters flag accepts wildcards -- basename matching avoids path sensitivity

---name: coverage-reportdescription: Generate a .NET code coverage report scoped to files changed in the current branch. Runs tests with coverage collection and produces filtered HTML reports.---# Code Coverage ReportGenerate a code coverage report scoped to source files changed in the current branch compared to a base branch.## Workflow### 1. Determine base branchDetect the base branch to diff against. Use the MR/PR target branch if known, otherwise default to `main` or `master` (whichever exists). Ask the user if ambiguous.```bashgit merge-base --fork-point main HEAD || git merge-base --fork-point master HEAD```### 2. Detect changed source files```bashgit diff <base-branch> --name-only -- '*.cs'```Filter out test files (paths containing `Test`, `Tests`, `.Tests`, `.Test`).If no source files changed, stop and inform the user.### 3. Identify test project(s)Determine which test project(s) to run. Strategies (in order):1. **User-specified**: If the user names a test project, use it2. **Convention-based**: Look for test projects whose name matches the changed project (e.g., `MyProject` -> `MyProject.Tests`)3. **Solution-wide**: Run all tests in the solution if scope is unclear4. **Ask**: If ambiguous, ask the user which test project(s) to run### 4. Clean previous results```bashrm -rf TestResults/```### 5. Run tests with coverage```bashdotnet test <test-project-or-solution> \ --collect:"XPlat Code Coverage" \ --results-directory ./TestResults/```### 6. Build file filtersFrom the changed file list (step 2), extract basenames and build a filter string:```+*FileName1.cs;+*FileName2.cs;+*FileName3.cs```### 7. Generate report```bashdotnet reportgenerator \ -reports:"TestResults/**/coverage.cobertura.xml" \ -targetdir:"TestResults/CoverageReport" \ -reporttypes:"Html;TextSummary" \ -filefilters:"<filters>"```### 8. Display results1. Print `TestResults/CoverageReport/Summary.txt` to the terminal2. Open the HTML report (platform-aware): - Windows: `start TestResults/CoverageReport/index.html` - macOS: `open TestResults/CoverageReport/index.html` - Linux: `xdg-open TestResults/CoverageReport/index.html`## Tips- For large solutions, scope to specific test projects to speed up collection- The `-filefilters` flag accepts wildcards -- basename matching avoids path sensitivity

Frequently asked questions

Coverage Report