dotnet-complexity
Use free built-in .NET maintainability analyzers and code metrics configuration to find overly complex methods and coupled code. Use when a repo needs cyclomatic complexity checks, maintainability thresholds, or complexity-driven refactoring gates.
Install
npx skills add https://github.com/Postpartum-genushyacinthus29/dotnet-skills/tree/main/skills/dotnet-complexity
claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install postpartum-genushyacinthus29-dotnet-skills@llmmart
git clone https://github.com/Postpartum-genushyacinthus29/dotnet-skills.git
The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole postpartum-genushyacinthus29/dotnet-skills collection as a plugin from our marketplace. Git is the plain clone.
Skill manifest
.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.mdand confirm scope and constraints. - Run this skill's
Workflowthrough theRalph Loopuntil outcomes are acceptable. - Return the
Required Result Formatwith concrete artifacts and verification evidence.
Workflow
- Start with the built-in maintainability analyzers before reaching for non-standard tooling.
- Use these rules deliberately:
CA1502for excessive cyclomatic complexity in methodsCA1505for low maintainability indexCA1506for excessive class couplingCA1501when inheritance depth is also part of the design problem
- Keep rule severity in the root
.editorconfig. - Keep metric thresholds in a checked-in
CodeMetricsConfig.txtadded asAdditionalFiles. - Pair analyzer findings with MCAF maintainability limits in
AGENTS.md.
Bootstrap When Missing
If complexity thresholds are not configured yet:
- Detect current state:
rg -n "CA1501|CA1502|CA1505|CA1506|CodeMetricsConfig" -g '.editorconfig' -g '*.csproj' -g 'Directory.Build.*' .rg --files -g 'CodeMetricsConfig.txt'
- Add severity entries for
CA1502,CA1505,CA1506, andCA1501in root.editorconfig. - Add checked-in
CodeMetricsConfig.txtand include it asAdditionalFilesin project props. - Keep maintainability limits aligned with
AGENTS.md. - Run
dotnet build SOLUTION_OR_PROJECTand returnstatus: configuredorstatus: improved. - If policy relies only on
AGENTS.mdlimits with no analyzer gate by design, returnstatus: not_applicable.
Deliver
- explicit complexity and maintainability policy
- checked-in metric thresholds
- CI commands that surface complex methods early
Validate
- method-complexity checks are enabled where the repo wants them
- thresholds are versioned in repo, not held in IDE memory
- complexity findings map to real refactoring decisions
Ralph Loop
Use the Ralph Loop for every task, including docs, architecture, testing, and tooling work.
- Plan first (mandatory):
- analyze current state
- define target outcome, constraints, and risks
- write a detailed execution plan
- list final validation skills to run at the end, with order and reason
- Execute one planned step and produce a concrete delta.
- Review the result and capture findings with actionable next fixes.
- Apply fixes in small batches and rerun the relevant checks or review steps.
- Update the plan after each iteration.
- Repeat until outcomes are acceptable or only explicit exceptions remain.
- If a dependency is missing, bootstrap it or return
status: not_applicablewith explicit reason and fallback path.
Required Result Format
status:complete|clean|improved|configured|not_applicable|blockedplan: concise plan and current iteration stepactions_taken: concrete changes madevalidation_skills: final skills run, or skipped with reasonsverification: commands, checks, or review evidence summaryremaining: top unresolved items ornone
For setup-only requests with no execution, return status: configured and exact next commands.
Load References
references/complexity.mdreferences/metrics.mdreferences/config.md
Example Requests
- "Which analyzer finds complex methods in .NET?"
- "Add a complexity gate for our C# code."
- "Configure cyclomatic complexity thresholds."
Files (dotnet-skills)
-
references
-
complexity.md 2.3 KB
Loading… -
config.md 5.4 KB
Loading… -
metrics.md 4.1 KB
Loading…
-
-
SKILL.md 4.4 KB
--- name: dotnet-complexity version: "1.0.0" category: "Metrics" description: "Use free built-in .NET maintainability analyzers and code metrics configuration to find overly complex methods and coupled code. Use when a repo needs cyclomatic complexity checks, maintainability thresholds, or complexity-driven refactoring gates." compatibility: "Requires a .NET SDK-based repository; respects the repo's `AGENTS.md` commands first." --- # .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 1. Read the nearest `AGENTS.md` and confirm scope and constraints. 2. Run this skill's `Workflow` through the `Ralph Loop` until outcomes are acceptable. 3. Return the `Required Result Format` with concrete artifacts and verification evidence. ## Workflow 1. Start with the built-in maintainability analyzers before reaching for non-standard tooling. 2. 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 3. Keep rule severity in the root `.editorconfig`. 4. Keep metric thresholds in a checked-in `CodeMetricsConfig.txt` added as `AdditionalFiles`. 5. Pair analyzer findings with MCAF maintainability limits in `AGENTS.md`. ## Bootstrap When Missing If complexity thresholds are not configured yet: 1. Detect current state: - `rg -n "CA1501|CA1502|CA1505|CA1506|CodeMetricsConfig" -g '.editorconfig' -g '*.csproj' -g 'Directory.Build.*' .` - `rg --files -g 'CodeMetricsConfig.txt'` 2. Add severity entries for `CA1502`, `CA1505`, `CA1506`, and `CA1501` in root `.editorconfig`. 3. Add checked-in `CodeMetricsConfig.txt` and include it as `AdditionalFiles` in project props. 4. Keep maintainability limits aligned with `AGENTS.md`. 5. Run `dotnet build SOLUTION_OR_PROJECT` and return `status: configured` or `status: improved`. 6. If policy relies only on `AGENTS.md` limits with no analyzer gate by design, return `status: not_applicable`. ## Deliver - explicit complexity and maintainability policy - checked-in metric thresholds - CI commands that surface complex methods early ## Validate - method-complexity checks are enabled where the repo wants them - thresholds are versioned in repo, not held in IDE memory - complexity findings map to real refactoring decisions ## Ralph Loop Use the Ralph Loop for every task, including docs, architecture, testing, and tooling work. 1. Plan first (mandatory): - analyze current state - define target outcome, constraints, and risks - write a detailed execution plan - list final validation skills to run at the end, with order and reason 2. Execute one planned step and produce a concrete delta. 3. Review the result and capture findings with actionable next fixes. 4. Apply fixes in small batches and rerun the relevant checks or review steps. 5. Update the plan after each iteration. 6. Repeat until outcomes are acceptable or only explicit exceptions remain. 7. If a dependency is missing, bootstrap it or return `status: not_applicable` with explicit reason and fallback path. ### Required Result Format - `status`: `complete` | `clean` | `improved` | `configured` | `not_applicable` | `blocked` - `plan`: concise plan and current iteration step - `actions_taken`: concrete changes made - `validation_skills`: final skills run, or skipped with reasons - `verification`: commands, checks, or review evidence summary - `remaining`: top unresolved items or `none` For setup-only requests with no execution, return `status: configured` and exact next commands. ## Load References - `references/complexity.md` - `references/metrics.md` - `references/config.md` ## Example Requests - "Which analyzer finds complex methods in .NET?" - "Add a complexity gate for our C# code." - "Configure cyclomatic complexity thresholds."
Comments (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.