agentleFS
Postpartum-genushyacinthus29Postpartum-genushyacinthus29/dotnet-skills/skills/dotnet-coverlet/SKILL.md

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.

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
  1. Distinctive:

    leave reusable project context so future tasks are faster and safer

    line 21
  2. Distinctive:

    Read the nearest AGENTS.md and confirm scope and constraints.

    line 36
  3. Very specific:

    Run this skill's Workflow through the Ralph Loop until outcomes are acceptable.

    line 37
  4. Distinctive:

    Add coverage packages only to test projects.

    line 46
  5. Very specific:

    Do not mix coverlet.collector and coverlet.msbuild in the same test project.

    line 47
  6. Distinctive:

    If coverage is not configured yet:

    line 52
  7. Very specific:

    Run the chosen command once and return status: configured or status: improved.

    line 67
  8. Very specific:

    If another coverage engine already owns coverage for this repo, return status: not_applicable.

    line 68
  9. Distinctive:

    Use the Ralph Loop for every task, including docs, architecture, testing, and tooling work.

    line 82
  10. Distinctive:

    write a detailed execution plan

    line 87
  11. Distinctive:

    Update the plan after each iteration.

    line 92
  12. Very specific:

    If a dependency is missing, bootstrap it or return status: not_applicable with explicit reason and fallback path.

    line 94

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
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, or coverlet.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

  1. Read the nearest AGENTS.md and confirm scope and constraints.
  2. Run this skill's Workflow through the Ralph Loop until outcomes are acceptable.
  3. Return the Required Result Format with concrete artifacts and verification evidence.

Workflow

  1. Choose the driver deliberately:
    • coverlet.collector for VSTest dotnet test --collect
    • coverlet.msbuild for MSBuild property-driven runs
    • coverlet.console for standalone scenarios
  2. Add coverage packages only to test projects.
  3. Do not mix coverlet.collector and coverlet.msbuild in the same test project.
  4. Pair raw coverage collection with ReportGenerator only when humans need rendered reports.

Bootstrap When Missing

If coverage is not configured yet:

  1. 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
  2. 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
  3. 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"
  4. Run the chosen command once and return status: configured or status: improved.
  5. 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.

  1. 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
  2. Execute one planned step and produce a concrete delta.
  3. Review the result and capture findings with actionable next fixes.
  4. Apply fixes in small batches and rerun the relevant checks or review steps.
  5. Update the plan after each iteration.
  6. Repeat until outcomes are acceptable or only explicit exceptions remain.
  7. If a dependency is missing, bootstrap it or return status: not_applicable with explicit reason and fallback path.

Required Result Format

  • status: complete | clean | improved | configured | not_applicable | blocked
  • plan: concise plan and current iteration step
  • actions_taken: concrete changes made
  • validation_skills: final skills run, or skipped with reasons
  • verification: commands, checks, or review evidence summary
  • remaining: top unresolved items or none

For setup-only requests with no execution, return status: configured and exact next commands.

Load References

  • references/commands.md
  • references/patterns.md
  • references/coverlet.md

Example Requests

  • "Add Coverlet to this .NET solution."
  • "Choose the right Coverlet driver for CI."

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.