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.collector for VSTest dotnet test --collect - coverlet.msbuild for MSBuild property-driven runs - coverlet.console for 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 --local - dotnet tool list --global - command -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) and dotnet tool install coverlet.console
- 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"
- 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."