mcaf-dotnet-coverlet

Automate Coverlet integration for .NET line and branch coverage analysis.

4|Updated Mar 6, 2026

Search Tags:#testing #code coverage #dotnet #ci #msbuild #coverlet

Ready to run

npx skills add https://github.com/managedcode/MCPGateway --skill mcaf-dotnet-coverlet

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: mcaf-dotnet-coverlet
Source: https://github.com/managedcode/MCPGateway/tree/main/.codex/skills/mcaf-dotnet-coverlet
Command: npx skills add https://github.com/managedcode/MCPGateway --skill mcaf-dotnet-coverlet

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the need for robust code coverage in .NET projects, ensuring that tests adequately cover the codebase and providing essential metrics for CI/CD pipelines.

Core Features & Use Cases

Line and Branch Coverage: Generates detailed coverage reports.
Driver Selection: Allows choosing between coverlet.collector, coverlet.msbuild, or coverlet.console for flexibility.
CI Integration: Provides commands suitable for continuous integration environments.
Use Case: Integrate Coverlet into your .NET test suite to automatically generate coverage reports during your CI build, flagging areas of the code that lack sufficient testing.

Quick Start

Add the coverlet.collector package to your .NET test project and configure your CI pipeline to run tests with coverage collection enabled.

Frequently Asked Questions about mcaf-dotnet-coverlet

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate .NET code coverage with Coverlet in a CI pipeline?▼

You can automate .NET code coverage by integrating the Coverlet toolchain into your CI pipeline to collect line and branch metrics and generate reproducible coverage artifacts during builds.

What is the difference between coverlet.collector, coverlet.msbuild, and coverlet.console drivers?▼

Coverlet drivers differ by integration approach: collector integrates with the .NET test platform, MSBuild hooks into the build process, and console runs as a standalone tool, offering flexible driver selection for various testing scenarios.

Does Coverlet support both line and branch coverage metrics for .NET projects?▼

Coverlet supports detailed line and branch coverage metrics for .NET projects, ensuring tests adequately cover the codebase and providing essential measurement data for CI/CD pipelines.

Can I use Coverlet to generate reproducible code coverage artifacts in continuous integration?▼

Coverlet ensures CI-safe coverage commands and reproducible artifact generation, allowing you to reliably produce consistent code coverage reports within your continuous integration environments.

What's the best way to integrate code coverage into an existing .NET test suite?▼

The best way to integrate code coverage is adding the coverlet.collector package to your .NET test project and configuring your test runs to automatically generate coverage reports, flagging code lacking sufficient tests.

When do I need to configure driver selection for .NET code coverage collection?▼

You need to configure driver selection when adapting code coverage collection to specific testing scenarios, choosing between collector, MSBuild, or console drivers to match your project's build and test execution flow.