What problem does it solve? Raw coverage percentages tell you what code was executed but not which uncovered code is risky, why coverage has plateaued, or which methods are dangerous to refactor. This Skill turns a .NET solution or existing Cobertura XML into a prioritized risk-hotspot list using CRAP (Change Risk Anti-Patterns) scores. ## Core Features & Use Cases - CRAP Score Analysis: Computes CRAP = complexity² × (1 − coverage)³ + complexity per method and surfaces the top risk hotspots — complex code with low coverage. - Automated Coverage Collection: Auto-detects the coverage provider (coverlet.collector or Microsoft.Testing.Extensions.CodeCoverage), adds one if missing, and runs dotnet test with Cobertura output — no runsettings files needed. - Coverage Gap & Plateau Diagnosis: Extracts per-method coverage below thresholds, assigns HIGH/MED/LOW priorities, and identifies what is blocking coverage gains. - Use Case: Your project's line coverage is stuck at 72% and you don't know why. Run this Skill to get a ranked table showing that ProcessOrder has a CRAP score of 48 (complexity 12, 20% coverage), plus concrete recommendations on which tests to write next. ## Quick Start Analyze the code coverage and CRAP risk hotspots for the .NET solution in the current directory and tell me which methods are blocking coverage improvement.
