cck-de-sloppify

Run a seven-step cleanup pipeline on .NET codebases with build and test verification.

2|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/s205109/AHKFlowApp --skill cck-de-sloppify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cck-de-sloppify
Source: https://github.com/s205109/AHKFlowApp/tree/main/.claude/skills/cck-de-sloppify
Command: npx skills add https://github.com/s205109/AHKFlowApp --skill cck-de-sloppify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic code cleanup and debt reduction for .NET projects, replacing ad-hoc tidyups with a formal seven-step pipeline that ensures formatting, removal of unused usings, analyzer warning fixes, dead code elimination, TODO resolution, sealing non-inherited classes, and proper CancellationToken propagation, with independent verification between steps.

Core Features & Use Cases

  • A formal 7-step cleanup pipeline that runs Step 1: Format All Code, Step 2: Remove Unused Usings, Step 3: Fix Analyzer Warnings, Step 4: Remove Dead Code, Step 5: Resolve TODOs, Step 6: Seal Non-Inherited Classes, Step 7: Propagate CancellationToken; each step is verified via dotnet build/test and committed separately to preserve history.
  • Safe removals: dead code is only removed after safety checks (references, DI, serialization) to prevent breaking changes.
  • Applicable to ongoing maintenance and pre-release hygiene, ensuring consistent code quality and reduced tech debt.

Quick Start

Run the seven-step cleanup pipeline on your .NET solution and verify each step with a build and test.

Frequently Asked Questions about cck-de-sloppify

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

FAQPage Schema
How do I automate .NET codebase cleanup and tech debt reduction?

Automate .NET codebase cleanup by running a formal seven-step pipeline that handles formatting, unused usings, analyzer warnings, dead code, TODOs, class sealing, and CancellationToken propagation. Each step is verified with dotnet build and test, then committed separately to ensure safe, incremental improvements.

What is the safest way to remove dead code in a C# solution?

Safe dead code removal in a C# solution requires checking references, dependency injection, and serialization before deletion. This automated pipeline executes those safety checks to prevent breaking changes, verifying the build and tests pass before committing the removal.

Does this .NET cleanup pipeline work for ongoing maintenance on large solutions?

Yes, this .NET cleanup pipeline is designed for ongoing maintenance across large solutions. It applies a defined seven-step sequence with per-step verification and explicit commit boundaries, ensuring consistent code quality and reduced tech debt without disrupting development.

What are the limitations of automating C# refactoring with this cleanup pipeline?

The main constraint of this C# refactoring pipeline is its sequential dependency: each of the seven steps requires a successful dotnet build and test before proceeding. Additionally, dead code removal is gated by strict safety checks, limiting removal to verified non-breaking changes.