crap-score

# CRAP Score Analysis Calculate CRAP (Change Risk Anti-Patterns) scores for .NET methods to identify code that is both complex and undertested. ## Background The CRAP score combines **cyclomatic complexity** and **code coverage** into a single metric: $$\text{CRAP}(m) = \text{comp}(m)^2 \times (1 - \text{cov}(m))^3 + \text{comp}(m)$$ Where: - $\text{comp}(m)$ = cyclomatic complexity of method $m$ - $\text{cov}(m)$ = code coverage ratio (0.0 to 1.0) of method $m$ | CRAP Score | Risk Level | Interpretation | |------------|------------|----------------| | < 5 | Low | Simple and well-tested | | 5-15 | Moderate | Acceptable for most code | | 15-30 | High | Needs more tests or simplification | | > 30 | Critical | Refactor and add coverage urgently | A method with 100% coverage has CRAP = complexity (the minimum). A method with 0% coverage has CRAP = complexity^2 + complexity. ## When to Use - User wants to assess which methods are risky due to low coverage and high complexity - User asks for CRAP score of specific methods, classes, or files - User wants to prioritize which code to test next - User wants to evaluate test quality beyond simple coverage percentages ## When Not to Use - User just wants to run tests (use `run-tests` skill) - User wants to write new tests (use `writing-mstest-tests` skill or general coding assistance) - User only wants a coverage percentage without complexity analysis ## Inputs | Input | Required | De...