Coverage Analysis skill: what it does and how to install it
Analyses .NET coverage evidence, reconciles line and branch targets, identifies blockers, and ranks CRAP risk when explicitly requested.
Summary generated from the skill's documentation.
Install
$ npx skills add dotnet/skills --skill coverage-analysisRun it in a terminal. If your agent is already running, start a new session so it picks the skill up.
About this skill
What it does. Analyses supplied .NET line, branch and condition coverage or collects Cobertura when analysis needs data, then reconciles totals, target arithmetic and blocking members. It can rank project-wide CRAP and refactoring-risk hotspots only when explicitly requested, and produces saved reports only when asked.
When to use it. Use it for coverage gaps, plateaus and project-wide risk analysis. It does not write tests, handle named-member CRAP analysis, test tagging, untested-source discovery, general test runs, or non-.NET coverage collection.
History
Repo stars
5.6kAbout +410 since 9 Jul 2026
Before 1 Oct 2026 the curve is estimated from public event data.
Stars are counted for the whole repository, which holds 43 skills.
Show as a table
| Date | Repo stars |
|---|---|
| 5 Oct 2026 | 5,557 |
| 4 Oct 2026 | 5,551 |
| 3 Oct 2026 | 5,543 |
| 2 Oct 2026 | 5,540 |
| 1 Oct 2026 | 5,531 |
| 24 Sept 2026 (estimated) | 5,519 |
| 17 Sept 2026 (estimated) | 5,494 |
| 10 Sept 2026 (estimated) | 5,419 |
| 3 Sept 2026 (estimated) | 5,258 |
| 27 Aug 2026 (estimated) | 5,233 |
| 20 Aug 2026 (estimated) | 5,221 |
| 13 Aug 2026 (estimated) | 5,221 |
| 6 Aug 2026 (estimated) | 5,171 |
| 30 Jul 2026 (estimated) | 5,159 |
| 23 Jul 2026 (estimated) | 5,159 |
| 16 Jul 2026 (estimated) | 5,147 |
| 9 Jul 2026 (estimated) | 5,147 |
Installs
2.7k
Tracking since . A chart appears once there are 7 days of data.
Installs via skills.sh
Similar skills
- Finishing a Development BranchGuides the choice of how to integrate finished work once tests pass: merge, pull request or cleanup.
- Code ReviewReviews the changes since a commit or branch on two axes: the repo's coding standards and the originating spec.
- Browser Use QAQA-tests a website or web app in a browser and returns a 1–5 quality score with evidence.