Agent skill
dotnet-coverlet
Use the open-source free `coverlet` toolchain for .NET code coverage. Use when a repo needs line and branch coverage, collector versus MSBuild driver selection, or CI-safe coverage commands.
Install this agent skill to your Project
npx add-skill https://github.com/managedcode/dotnet-skills/tree/main/catalog/Testing/Coverlet/skills/dotnet-coverlet
SKILL.md
Coverlet for .NET
Trigger On
- the repo uses or wants
coverlet - CI needs line or branch coverage for .NET tests
- the team needs to choose between
coverlet.collector,coverlet.msbuild, orcoverlet.console
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
- coverage report rendering by itself
- repos that intentionally use a different coverage engine
Inputs
- the nearest
AGENTS.md - active runner model: VSTest or Microsoft.Testing.Platform
- target test projects
Quick Start
- Read the nearest
AGENTS.mdand confirm scope and constraints. - Run this skill's
Workflowthrough theRalph Loopuntil outcomes are acceptable. - Return the
Required Result Formatwith concrete artifacts and verification evidence.
Workflow
- Choose the driver deliberately:
coverlet.collectorfor VSTestdotnet test --collectcoverlet.msbuildfor MSBuild property-driven runscoverlet.consolefor standalone scenarios
- Add coverage packages only to test projects.
- Do not mix
coverlet.collectorandcoverlet.msbuildin the same test project. - Pair raw coverage collection with
ReportGeneratoronly when humans need rendered reports.
Bootstrap When Missing
If coverage is not configured yet:
- Detect current state:
rg -n "coverlet\\.(collector|msbuild)|CollectCoverage|XPlat Code Coverage" -g '*.csproj' -g '*.props' -g '*.targets' .dotnet tool list --localdotnet tool list --globalcommand -v coverlet
- Install exactly one driver path:
- VSTest collector:
dotnet add TEST_PROJECT.csproj package coverlet.collector - MSBuild driver:
dotnet add TEST_PROJECT.csproj package coverlet.msbuild - Console tool:
dotnet new tool-manifest(if missing) anddotnet tool install coverlet.console
- VSTest collector:
- Record one concrete local and CI command in
AGENTS.md:- collector:
dotnet test TEST_PROJECT.csproj --collect:"XPlat Code Coverage" - msbuild:
dotnet test TEST_PROJECT.csproj /p:CollectCoverage=true /p:CoverletOutputFormat=cobertura - console:
dotnet tool run coverlet TEST_ASSEMBLY.dll --target "dotnet" --targetargs "test TEST_PROJECT.csproj --no-build"
- collector:
- Run the chosen command once and return
status: configuredorstatus: improved. - If another coverage engine already owns coverage for this repo, return
status: not_applicable.
Deliver
- explicit coverage driver selection
- reproducible coverage commands for local and CI runs
Validate
- coverage driver matches the runner model
- coverage files are stable and consumable by downstream reporting
Ralph Loop
Use the Ralph Loop for every task, including docs, architecture, testing, and tooling work.
- Plan first (mandatory):
- analyze current state
- define target outcome, constraints, and risks
- write a detailed execution plan
- list final validation skills to run at the end, with order and reason
- Execute one planned step and produce a concrete delta.
- Review the result and capture findings with actionable next fixes.
- Apply fixes in small batches and rerun the relevant checks or review steps.
- Update the plan after each iteration.
- Repeat until outcomes are acceptable or only explicit exceptions remain.
- If a dependency is missing, bootstrap it or return
status: not_applicablewith explicit reason and fallback path.
Required Result Format
status:complete|clean|improved|configured|not_applicable|blockedplan: concise plan and current iteration stepactions_taken: concrete changes madevalidation_skills: final skills run, or skipped with reasonsverification: commands, checks, or review evidence summaryremaining: top unresolved items ornone
For setup-only requests with no execution, return status: configured and exact next commands.
Load References
references/commands.mdreferences/patterns.mdreferences/coverlet.md
Example Requests
- "Add Coverlet to this .NET solution."
- "Choose the right Coverlet driver for CI."
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
dotnet-project-setup
Create or reorganize .NET solutions with clean project boundaries, repeatable SDK settings, and a maintainable baseline for libraries, apps, tests, CI, and local development.
csharp-scripts
Run single-file C# programs as scripts (file-based apps) for quick experimentation, prototyping, and concept testing. Use when the user wants to write and execute a small C# program without creating a full project.
dotnet-pinvoke
Correctly call native (C/C++) libraries from .NET using P/Invoke and LibraryImport. Covers function signatures, string marshalling, memory lifetime, SafeHandle, and cross-platform patterns. USE FOR: writing new P/Invoke or LibraryImport declarations, reviewing or debugging existing native interop code, wrapping a C or C++ library for use in .NET, diagnosing crashes, memory leaks, or corruption at the managed/native boundary. DO NOT USE FOR: COM interop, C++/CLI mixed-mode assemblies, or pure managed code with no native dependencies.
nuget-trusted-publishing
Set up NuGet trusted publishing (OIDC) on a GitHub Actions repo — replaces long-lived API keys with short-lived tokens. USE FOR: trusted publishing, NuGet OIDC, keyless NuGet publish, migrate from NuGet API key, NuGet/login, secure NuGet publishing. DO NOT USE FOR: publishing to private feeds or Azure Artifacts (OIDC is nuget.org only). INVOKES: shell (powershell or bash), edit, create, ask_user for guided repo setup.
dotnet-legacy-aspnet
Maintain classic ASP.NET applications on .NET Framework, including Web Forms, older MVC, and legacy hosting patterns, while planning realistic modernization boundaries.
dotnet-code-review
Review .NET changes for bugs, regressions, architectural drift, missing tests, incorrect async or disposal behavior, and platform-specific pitfalls before you approve or merge them.
Didn't find tool you were looking for?