skills.rest
Trossitec
TrossitecOFFICIAL
Explore all skills by this author →
WebsiteGitHub

de-sloppify

Run a seven-step .NET cleanup pipeline with build and test verification between phases.

1|Updated Apr 28, 2026
Search Tags:#refactoring#dotnet#dead code#code cleanup#roslyn#cancellationtoken#analyzer warnings
One-click install
npx skills add https://github.com/Trossitec/dotnet-claude-kit --skill de-sloppify-trossitec
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: de-sloppify
Source: https://github.com/Trossitec/dotnet-claude-kit/tree/main/skills/de-sloppify
Command: npx skills add https://github.com/Trossitec/dotnet-claude-kit --skill de-sloppify-trossitec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

De-sloppify removes accumulated .NET tech debt—formatting drift, unused usings, analyzer warnings, dead code, TODO clutter, non-inherited classes, and missing CancellationToken propagation—while minimizing the risk of breaking builds and tests.

Core Features & Use Cases

  • Run a 7-step, ordered cleanup pipeline to avoid random churn and keep changes reviewable (formatting, unused usings, analyzer warnings, dead code removal, TODO resolution, sealed class audit, CancellationToken propagation).
  • Verify after each phase using build and tests so cleanup is safe and reversible (commit between phases).
  • Use guardrails for risky changes with explicit safety checks before dead-code removal (reference checks, grep for string-based usage, DI/serialization/config checks).

Quick Start

Use the de-sloppify skill when you want to clean up a .NET solution by running a verified cleanup pass for “de-sloppify” and related housekeeping terms.

Frequently Asked Questions about de-sloppify

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

FAQPage Schema
How do I clean up .NET code and remove analyzer warnings safely?▼

You can clean up .NET code by running a 7-step ordered pipeline that fixes formatting, unused usings, analyzer warnings, dead code, and CancellationToken propagation with build and test verification between each phase.

What's the best way to propagate CancellationToken through .NET async endpoints and handlers?▼

CancellationToken propagation is handled by systematically passing tokens through endpoints, handlers, and data access calls within a structured cleanup pipeline that verifies builds and tests after each phase.

How do I safely remove dead code from a .NET solution without breaking dependencies?▼

Safe dead code removal requires explicit reference checks, grep for string-based usage, and DI, serialization, and config checks before deletion, all followed by build and test verification to ensure nothing breaks.

Can I use this code cleanup approach for tech-debt sprints and pre-release hardening?▼

Yes, this cleanup pipeline targets remediation workflows like tech-debt sprints, post-merge cleanup, warning burn-down, and pre-release hardening by coordinating multiple cleanup concerns sequentially with safety guardrails.

Does the .NET cleanup pipeline handle TODO clutter and non-inherited classes?▼

Yes, the pipeline includes dedicated phases for TODO hygiene resolution and sealed class audits, ensuring class design improvements are applied alongside formatting and diagnostic fixes with verification.

Related Skills

Explore More Software Engineering Skills→
rudironsonirudironsoni

dotnet-build-analysis

Interpret .NET build diagnostics and provide fix guidance for MSBuild, NuGet, and Roslyn errors.

Community
Intermediate
tsukumijimatsukumijima
18

konomitv-to-nx-jikkyo-porter

Port KonomiTV enhancements to NX-Jikkyo via diff review and dead-code removal.

Community
Advanced
dotnetdotnet
20.6k

analyzer-codefix

Implement Roslyn analyzers, code fixes, and refactorings with testing patterns.

Official
Advanced
dralgorhythmdralgorhythm
111

refactoring-code

Refactor code with Serena tools while keeping tests green.

Community
Intermediate