crap-analysis

Compute CRAP scores from OpenCover coverage and complexity data for .NET projects.

1|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/woutervanranst/Arius7 --skill crap-analysis-woutervanranst
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: crap-analysis
Source: https://github.com/woutervanranst/Arius7/tree/main/.agents/skills/crap-analysis
Command: npx skills add https://github.com/woutervanranst/Arius7 --skill crap-analysis-woutervanranst

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify high-risk code by computing CRAP scores from coverage and complexity data to guide testing and refactoring decisions.

Core Features & Use Cases

  • CRAP score calculation from OpenCover-compatible outputs and a scoring formula to quantify risk.
  • Surface risk hotspots across methods and modules to prioritize testing and refactoring.
  • CI/CD integration to surface CRAP-based quality gates and automate risk reporting.

Quick Start

Run the CRAP analysis workflow on your .NET project to generate risk hotspots from coverage and complexity metrics.

Frequently Asked Questions about crap-analysis

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

FAQPage Schema
How do I calculate CRAP scores to find risk hotspots in .NET projects?

Calculate CRAP scores by processing OpenCover-compatible coverage outputs and applying a scoring formula to quantify risk. This surfaces risk hotspots across methods and modules, directly guiding your testing and refactoring decisions.

What is a CRAP score and how does it identify risky code?

A CRAP score identifies risky code by combining code coverage and cyclomatic complexity metrics into a single risk quantification. High scores surface specific methods and modules where refactoring and additional testing are most critical.

Does CRAP analysis work with OpenCover and ReportGenerator for .NET?

Yes, CRAP analysis works with OpenCover-formatted reports and ReportGenerator. It requires coverage data, a CRAP scoring formula, and tooling like a dotnet-based test runner to surface risk hotspots across your .NET modules.

Can I integrate CRAP score reporting into CI/CD pipelines for .NET?

Yes, you can integrate CRAP analysis into CI/CD pipelines. It surfaces CRAP-based quality gates and automates risk reporting by computing scores from coverage and complexity data generated during your dotnet test runs.

Why use CRAP scores instead of just code coverage to guide refactoring?

Use CRAP scores instead of coverage alone because they factor in code complexity. This combination accurately surfaces true risk hotspots—highly complex untested methods—ensuring refactoring targets areas with the highest defect potential.