This walks you through setting up CRAP score analysis for .NET projects, which combines cyclomatic complexity with test coverage to find risky code (the formula is complexity times one minus coverage squared). The guide is thorough on the mechanics: you need OpenCover format specifically because it includes complexity metrics, ReportGenerator to build the HTML reports, and a proper runsettings file to exclude generated code and test assemblies. The Risk Hotspots section in the output is what you're after, showing methods with high complexity and low coverage that are dangerous to touch. Useful if you're inheriting a codebase or need to justify where testing effort should go. The threshold recommendations are reasonable: CRAP scores over 30 need immediate attention.
npx skills add https://github.com/aaronontheweb/dotnet-skills --skill crap-analysis