One-click install
npx skills add https://github.com/Maj3D10/Training-Platform --skill de-sloppify-maj3d10
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: de-sloppify
Source: https://github.com/Maj3D10/Training-Platform/tree/main/.agent/skills/de-sloppify
Command: npx skills add https://github.com/Maj3D10/Training-Platform --skill de-sloppify-maj3d10

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves accumulated .NET codebase “sloppiness” by running a disciplined cleanup pipeline that reduces warnings and dead code while minimizing the risk of breaking builds or tests.

Core Features & Use Cases

  • 7-step verified cleanup pipeline: formats code, removes unused usings, fixes analyzer warnings, removes dead code safely, resolves TODOs, audits for sealed classes, and propagates CancellationToken through async chains.
  • Safety-checked dead code removal: verifies compile-time references and also checks likely reflection/DI/serialization/string-based usages before deleting.
  • Operational rigor: enforces verification between phases (build + test) and recommends committing each step separately for easy rollback.

Use it when you need to pay down tech debt after feature merges, before a release, or to reduce CI noise by eliminating warnings and improving async responsiveness.

Quick Start

Ask the AI to run the de-sloppify pipeline for your .NET solution to format the code, fix analyzer warnings, remove dead code safely, seal eligible classes, and propagate CancellationToken end-to-end, verifying with dotnet build and dotnet test after each step.

Frequently Asked Questions about de-sloppify

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

FAQPage Schema
How do I safely remove dead code in a .NET solution without breaking reflection or dependency injection?

Safe dead code removal in .NET requires checking compile-time references and likely reflection, DI, serialization, and string-based usages before deleting. The de-sloppify pipeline verifies these patterns and runs dotnet build and test after each phase to prevent breaking changes.

What is the best way to reduce analyzer warnings across a .NET codebase before a release?

To reduce analyzer warnings before a release, run a structured cleanup pipeline that formats code, removes unused usings, and fixes analyzer warnings systematically. Verify the solution with dotnet build and dotnet test after each step to ensure stability.

How do I propagate CancellationToken through async chains in .NET?

CancellationToken propagation in .NET async chains is handled by auditing and threading the token through async methods end-to-end. The de-sloppify pipeline includes this as a step, verifying with dotnet build and dotnet test to ensure async responsiveness is improved safely.

Does the de-sloppify .NET cleanup workflow require committing changes after every step?

The de-sloppify .NET cleanup workflow recommends committing each step separately for easy rollback. This operational rigor ensures that if a build or test fails after a phase like dead code removal, you can revert without losing prior formatting or analyzer warning fixes.

Can I seal eligible classes in .NET without manually checking the entire codebase?

Sealing eligible classes in .NET can be automated by auditing the codebase for classes that have no inheritors. The de-sloppify pipeline includes a class auditing step that identifies and seals eligible classes, followed by build and test verification.

How does a .NET code cleanup pipeline handle TODO clutter and unused usings?

A .NET code cleanup pipeline resolves TODO clutter and removes unused usings by formatting code and addressing TODOs as part of a 7-step verified workflow. Each phase is verified with dotnet build and dotnet test to maintain codebase stability.