crap-score

Run dotnet test with coverage collection to produce a Cobertura XML report, then compute cyclomatic complexity per method and apply the CRAP formula: complexity squared times (1 minus coverage) cubed, plus complexity. This Skill automates the full workflow.

A CRAP score below 5 indicates simple, well-tested code, while 5-15 is acceptable for most methods. Scores of 15-30 are high risk needing more tests or simplification, and anything above 30 is critical and should be refactored and covered urgently.

The analysis works with Cobertura XML output from coverlet.collector via the XPlat Code Coverage collector, or from Microsoft.Testing.Extensions.CodeCoverage on .NET 9 and later using the --coverage-output-format cobertura flag.

Cobertura XML may use compiler-generated names for async methods, lambdas, and local functions. When names do not align, match methods by their line ranges in the coverage report instead of by name.

No. When cyclomatic complexity is 15 or higher, the minimum possible CRAP score equals the complexity itself, so coverage alone cannot bring it below the threshold. The method must be refactored, for example by extracting sub-methods, to reduce complexity first.

Avoid it for project-wide coverage analysis, diagnosing coverage plateaus, or deciding where to add tests across an entire solution. It is designed for targeted analysis of a named method, class, or single source file, not broad coverage strategy.