Systematic code cleanup pipeline for .NET projects. Runs 7 ordered steps: formatting, unused usings, analyzer warnings, dead code removal, TODO resolution, sealed class audit, and CancellationToken propagation. Each step is verified independently with tests between phases. Load this skill when: "cle

/de sloppify — 7 Step Cleanup Pipeline What Runs an ordered, verified cleanup pipeline over a .NET codebase. Order matters: formatting first (it touches every file — get the churn out of the way before anything else), dead code late (earlier steps reveal it). Random cleanup misses things and creates merge conflicts; the pipeline doesn't. Three rules make it safe: 1. Verify after each step — dotnet build + dotnet test between steps. A cleanup that breaks something is worse than the mess it was fixing. 2. Commit per step — each step is its own commit, so a bad Step 4 reverts without losing Steps 1 3. 3. Safe removals only — before deleting "dead" code, check for reflection, DI convention, and serialization usage that Roslyn cannot see. Per step commands, safety checklists, and code examples live in references/cleanup steps.md — read it before executing. When "Clean up", "tidy up", "de sloppify", "housekeeping", "tech debt" After a large feature merge or dependency upgrade (new warnings accumulate) Pre release hardening, or a scheduled quarterly cleanup sprint Before performance work (dead code out, classes sealed for devirtualization) Never mixed with feature work — cleanup commits stay pure How Step 0: Pick the Steps Scenario Steps to run Full cleanup pass / pre release / quarterly All 7 Quick tidy before PR 1, 2, 6 After large feature merge 1, 2, 3, 4 After dependency upgrade 2, 3 Before performance work 4, 6 CI warning threshold exceeded 3 only Tech debt sprint 4, 5 Steps 1 7 (execute in order, details in references/cleanup steps.md) Step Tool Commit message 1 Format all code dotnet format chore: apply dotnet format 2 Remove unused usings dotnet format analyzers diagnostics IDE0005 chore: remove unused using statements 3 Fix analyzer warnings MCP get diagnostics → triage by category chore: fix analyzer warnings 4 Remove dead code MCP find dead code + safety check (reflection/DI/serialization grep) chore: remove dead code 5 Resolve TODOs grep TODO/HACK/FIXME → fix, file issue, or delete chore: resolve TODO comments 6 Seal non inherited classes MCP get type hierarchy per candidate + test project grep chore: seal non inherited classes 7 Propagate CancellationToken MCP detect antipatterns → trace async chains chore: propagate CancellationToken through async chains After every step: dotnet build + dotnet test , then commit. If a step breaks the build or tests, fix or revert that step before continuing — never carry a red state into the next step. Delegate structural steps (4, 6, 7) to the refactor cleaner agent. Final Report Example Related references/cleanup steps.md — per step commands, safety checks, examples /verify — run the full verification pipeline after cleanup /health check — re grade the project to quantify the improvement /code review — cleanup handles style; review handles logic and design

de-sloppify