de-sloppify

Run a seven-step cleanup pipeline for .NET projects with per-step commits.

640|145|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/codewithmukesh/dotnet-claude-kit --skill de-sloppify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: de-sloppify
Source: https://github.com/codewithmukesh/dotnet-claude-kit/tree/main/skills/de-sloppify
Command: npx skills add https://github.com/codewithmukesh/dotnet-claude-kit --skill de-sloppify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reduce technical debt and brittle code by providing a repeatable, verified cleanup pipeline that removes noise, fixes analyzer warnings, and safely eliminates dead code without breaking the build or tests.

Core Features & Use Cases

  • Ordered 7-step pipeline that runs formatting, unused using removal, analyzer fixes, dead code removal, TODO triage, sealing of non-inherited classes, and CancellationToken propagation.
  • Safety-first checks including build and test verification after each step, explicit reflection and DI grep checks before removals, and one-commit-per-step discipline to enable safe reverts.
  • Real-world uses: pre-release hardening, PR tidy before review, quarterly maintenance sprints, and targeted tech-debt work such as sealing classes for devirtualization or propagating CancellationToken through async call chains.

Quick Start

Run the De-Sloppify pipeline across your solution and verify after each step by formatting the code, removing unused usings, fixing analyzer warnings, performing safety-checked dead code removals, resolving TODOs, sealing eligible classes, and adding CancellationToken propagation.

Frequently Asked Questions about de-sloppify

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

FAQPage Schema
How do I automate .NET code cleanup and dead code removal safely?

Automate .NET code cleanup using a 7-step pipeline that enforces formatting, analyzer fixes, and dead code removal. Safety checks verify builds, tests, reflection usage, and DI registration before removals, committing each step separately for safe reverts.

What is the best way to propagate CancellationToken through async .NET call chains?

Propagate CancellationToken through async .NET call chains using a systematic cleanup pipeline step. This enforces token threading across endpoints, services, and tests, verifying builds and tests after the modification to ensure safe async operations.

Can I seal non-inherited .NET classes without breaking my build or tests?

Yes, you can seal non-inherited .NET classes through a dedicated pipeline step that verifies build and test integrity after modifications. This devirtualization process is separated into explicit commits to enable safe reverts if issues arise.

How do I resolve TODOs and analyzer warnings across a .NET solution?

Resolve TODOs and analyzer warnings across a .NET solution by running a comprehensive cleanup pipeline that targets solution-wide scopes including endpoints, services, and tests. Each phase runs build and test verification to guarantee safe modifications.

What safety precautions are needed when removing dead code in .NET projects?

Dead code removal in .NET requires safety checks including build and test verification, explicit reflection grep checks, and dependency injection registration validation before removals. Each removal step gets its own explicit commit message to enable safe reverts.

Does the .NET cleanup pipeline support pre-release hardening and PR tidy before review?

Yes, the .NET cleanup pipeline supports pre-release hardening and PR tidy before review by running ordered steps like formatting, unused using removal, and analyzer fixes. It verifies builds and tests after each phase across solution-wide scopes.