Use free built-in .NET maintainability analyzers and code metrics configuration to find overly complex methods and coupled code. USE FOR: the team wants to find overly complex methods; cyclomatic complexity thresholds are needed in CI; maintainability metrics or coupling thresholds need to be configured. DO NOT USE FOR: formatting-only work; generic analyzer setup with no complexity policy change. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, o
SkillScore73Maintained
Automatic
◆Coding pack
Last verified 8/19/2026
What it changes
Passed 13 of 18 test cases with the skill, and 10 of 18 without it.
Without skill55%
With skill73%
Checks it passed that the model alone missed
Returns status as configured.
Populates the status field with configured.
Provides an explicit reason and fallback path.
and 5 more in the full report
6 fixed10 passed either way4 still failing2 broke
Pass-rate lift
+18 pp
Tokens
+21%
Agent turns
0%
Response time
-37%
Model gemini-3.6-flashMeasured 8/19/2026v116 of 22 cases passed with skill · 18 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 6
Prompt
For a setup-only query with no code changes, should we return status: completed or status: configured, and what else must be provided?
What was checked, without and with the skill
Checked
Without skill
With skill
Returns status as configured.
Missed
Passed
Includes exact next commands to run.
Passed
Passed
case-20 · gemini-3.6-flash · 8/19/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md107 lines4 files
.NET Complexity Review
Trigger On
the team wants to find overly complex methods
cyclomatic complexity thresholds are needed in CI
maintainability metrics or coupling thresholds need to be configured
Value
produce a concrete project delta: code, docs, config, tests, CI, or review artifact
reduce ambiguity through explicit planning, verification, and final validation skills
leave reusable project context so future tasks are faster and safer
Do Not Use For
formatting-only work
generic analyzer setup with no complexity policy change
Inputs
the nearest AGENTS.md
current analyzer settings
current maintainability limits
Quick Start
Read the nearest AGENTS.md and confirm scope and constraints.
Run this skill's Workflow through the Ralph Loop until outcomes are acceptable.
Return the Required Result Format with concrete artifacts and verification evidence.
Workflow
Start with the built-in maintainability analyzers before reaching for non-standard tooling.
Use these rules deliberately:
CA1502 for excessive cyclomatic complexity in methods
CA1505 for low maintainability index
CA1506 for excessive class coupling
CA1501 when inheritance depth is also part of the design problem
Calculates targeted CRAP (Change Risk Anti-Patterns) scores for a named .NET method, class, or single source file. Use when the user explicitly asks to compute CRAP scores or assess risky untested code for a specific target, combining Cobertura coverage data with cyclomatic complexity analysis. DO NOT USE FOR: project-wide coverage analysis, coverage plateau or "stuck coverage" diagnosis, what's blocking coverage, or where to add tests across a project (use coverage-analysis); writing tests; run