Identify code smells, coupling hotspots, and test gaps in .NET codebases.
npx skills add https://github.com/nobelk/claude-tools --skill dotnet-refactor
Please help me install this Agent Skill. Skill: dotnet-refactor Source: https://github.com/nobelk/claude-tools/tree/main/skills/dotnet-refactor Command: npx skills add https://github.com/nobelk/claude-tools --skill dotnet-refactor
Principal-level C#/.NET codebase refactoring skill. Use when the user asks to refactor, restructure, clean up, or improve the quality of a C# or .NET codebase. Triggers include: requests to implement design patterns, decouple tightly coupled code, improve logging, apply clean code or SOLID principles, improve maintainability, reduce technical debt, or modernize legacy .NET code. Also use when asked to generate a refactoring plan, identify code smells, or prepare a codebase for scaling. Covers unit test strategy for regression safety before and after refactoring.
Provide the codebase context and the refactor goal, and I will generate a phased refactoring plan.
High-intent search queries and answers about installing and using this skill.
To plan a phased .NET refactoring, you must identify code smells and coupling hotspots, establish a baseline test safety net, and generate a deployable plan focusing on one concern per commit with rollback strategies for each phase.
The best way to decouple tightly coupled C# code involves applying SOLID principles and design-pattern guidance to systematically reduce technical debt while maintaining regression safety through characterization tests for critical paths.
Yes, you need a baseline of existing unit tests before refactoring a C# project to ensure regression safety, alongside a plan for characterization tests to verify critical paths before and after structural changes.
Identifying code smells and coupling hotspots in a .NET application requires systematic discovery of dependencies and architectural flaws, checking SOLID adherence, logging gaps, and test coverage to inform a structured refactoring plan.
You can apply SOLID principles to modernize legacy .NET code safely by executing stepwise refactoring phases that are independently deployable, utilizing verification, rollback strategies, and post-refactor validation to prevent regressions.
A .NET refactoring plan needs rollback strategies for each phase to ensure that independently deployable changes can be safely reverted if post-refactor validation or characterization tests detect critical regression failures.
CANTAGESTUDIOIdentify missing tests and establish a minimal safety net before refactoring.
bostonaholicReview code for SOLID design violations and suggest refactoring steps.
velesarAnalyze and visualize software dependencies to detect coupling, cycles, and architectural violations.
azat-ioRestructure code in small steps while preserving external behavior with tests.
