coverage-fix

Diagnose and resolve Azure DevOps diff coverage failures for .NET pull requests.

Updated May 7, 2026
One-click install
npx skills add https://github.com/tmalcolm-0607/mad-council-claw --skill coverage-fix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coverage-fix
Source: https://github.com/tmalcolm-0607/mad-council-claw/tree/main/.claude/skills/coverage-fix
Command: npx skills add https://github.com/tmalcolm-0607/mad-council-claw --skill coverage-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the manual effort and PR blocking caused by Azure DevOps (ADO) diff coverage failures for .NET ecosystem pull requests, where changed lines must meet a 100% test coverage threshold to merge.

Core Features & Use Cases

  • Automated Gap Detection: Auto-identifies changed C# source files in a PR diff and cross-references them with ADO coverage reports to find uncovered lines.
  • Targeted Test Generation: Spawns specialized subagents to write precise unit tests for each uncovered code path, following explicit interface testing and naming conventions.
  • Iterative Verification: Runs coverage checks after each test push, iterating until the 100% diff coverage target is met or a bounded stop condition is reached.
  • Use Case: A developer submitting a PR to a .NET ecosystem repo can use this Skill to automatically resolve ADO coverage build failures without manually tracing uncovered lines or writing tests from scratch.

Quick Start

Invoke the coverage-fix skill to automatically diagnose and fix ADO diff coverage failures for your active ecosystem pull request.

Frequently Asked Questions about coverage-fix

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

FAQPage Schema
How do I fix Azure DevOps diff coverage failures for a .NET pull request?

Azure DevOps diff coverage failures for a .NET pull request can be resolved by automatically identifying uncovered changed C# files, generating targeted unit tests for those specific code paths, and iterating until the 100% coverage threshold is satisfied.

How does automated test gap remediation work for C# testing in ADO?

Automated test gap remediation for C# testing in ADO works by cross-referencing PR source file diffs against ADO coverage reports to pinpoint uncovered lines, then generating targeted unit tests and running iterative verification checks to close the gaps.

Can I automatically generate unit tests for uncovered code in a .NET repository?

Yes, you can automatically generate unit tests for uncovered code in a .NET repository by analyzing the ADO coverage report to detect specific uncovered code paths and spawning targeted subagents to write precise tests following explicit interface testing conventions.

Does this coverage automation tool work with any .NET ecosystem repository?

This coverage automation tool works specifically with .NET ecosystem repositories that have active Azure DevOps diff coverage policies enforcing 100% test coverage of changed lines for successful pull request merges.

What is the best way to achieve 100% diff coverage on changed C# source files?

The best way to achieve 100% diff coverage on changed C# source files is to automate gap detection and targeted test generation, running iterative verification checks after each test push until the policy requirement is fully satisfied.