dotnet-coverlet
Skill13 starsChanged 8 months agoMITView on GitHub
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.
In this repository84 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- dotnet-analyzer-configSkill
- dotnet-architectureSkill
- dotnet-archunitnetSkill
- dotnet-aspireSkill
- dotnet-aspnet-coreSkill
- dotnet-asynkron-profilerSkill
- dotnet-azure-functionsSkill
- dotnet-biomeSkill
- dotnet-blazorSkill
- dotnet-chousSkill
- dotnet-clocSkill
- dotnet-code-analysisSkill
- dotnet-codeqlSkill
- dotnet-code-reviewSkill
- dotnet-complexitySkill
- dotnet-csharpierSkill
- dotnet-entity-framework6Skill
- dotnet-entity-framework-coreSkill
- dotnet-eslintSkill
- dotnet-formatSkill
- dotnet-grpcSkill
- dotnet-htmlhintSkill
- dotnet-legacy-aspnetSkill
- dotnet-libvlcSkill
- dotnet-managedcode-communicationSkill
- dotnet-managedcode-markitdownSkill
- dotnet-managedcode-mimetypesSkill
- dotnet-managedcode-orleans-graphSkill
- dotnet-managedcode-orleans-signalrSkill
- dotnet-managedcode-storageSkill
- dotnet-mauiSkill
- dotnet-mcaf-agile-deliverySkill
- dotnet-mcaf-devexSkill
- dotnet-mcaf-documentationSkill
- dotnet-mcaf-feature-specSkill
- dotnet-mcaf-human-review-planningSkill
- dotnet-mcaf-ml-ai-deliverySkill
- dotnet-mcaf-nfrSkill
- dotnet-mcafSkill
- dotnet-mcaf-source-controlSkill
- dotnet-mcaf-ui-uxSkill
- dotnet-mcpSkill
- dotnet-metalintSkill
- dotnet-meziantou-analyzerSkill
- dotnet-microsoft-agent-frameworkSkill
- dotnet-microsoft-extensions-aiSkill
- dotnet-microsoft-extensionsSkill
- dotnet-minimal-apisSkill
- dotnet-mixed-realitySkill
- dotnet-mlnetSkill
- dotnet-modern-csharpSkill
- dotnet-mstestSkill
- dotnet-mvvmSkill
- dotnet-netarchtestSkill
- dotnet-nunitSkill
- dotnet-orleansSkill
- dotnet-profilingSkill
- dotnet-project-setupSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
12 rules. About 0 are common, 7 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 21
leave reusable project context so future tasks are faster and safer
- Distinctive: line 36
Read the nearest AGENTS.md and confirm scope and constraints.
- Very specific: line 37
Run this skill's Workflow through the Ralph Loop until outcomes are acceptable.
- Distinctive: line 46
Add coverage packages only to test projects.
- Very specific: line 47
Do not mix coverlet.collector and coverlet.msbuild in the same test project.
- Distinctive: line 52
If coverage is not configured yet:
- Very specific: line 67
Run the chosen command once and return status: configured or status: improved.
- Very specific: line 68
If another coverage engine already owns coverage for this repo, return status: not_applicable.
- Distinctive: line 82
Use the Ralph Loop for every task, including docs, architecture, testing, and tooling work.
- Distinctive: line 87
write a detailed execution plan
- Distinctive: line 92
Update the plan after each iteration.
- Very specific: line 94
If a dependency is missing, bootstrap it or return status: not_applicable with explicit reason and fallback path.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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."
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

