de-sloppify

Reviews recent code changes and removes dead code, debug artifacts, and over-engineering.

Updated May 22, 2026
One-click install
npx skills add https://github.com/kitfunso/claude-config --skill de-sloppify-kitfunso
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: de-sloppify
Source: https://github.com/kitfunso/claude-config/tree/main/skills/de-sloppify
Command: npx skills add https://github.com/kitfunso/claude-config --skill de-sloppify-kitfunso

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Asking an AI to implement a feature and keep it clean in one pass produces neither done well. This Skill separates the work into two passes: implement first, then run a dedicated cleanup review with fresh eyes on all changes. ## Core Features & Use Cases - Dead code removal: Deletes commented-out code, unused imports, and unreachable branches left over from implementation. - Debug artifact cleanup: Strips console.log, print(), and debugger statements before a PR. - Over-engineering detection: Simplifies abstractions with only one implementation, renames vague variables, and removes catch blocks that just re-throw. - Use Case: After a rapid prototyping session that touched 5 files, ask for a de-sloppify pass to remove leftover print statements, an unused strategy interface, and a vague temp variable before opening the pull request. ## Quick Start Review all the changes we just made and de-sloppify them by removing dead code, debug artifacts, and over-engineering, then run the test suite after cleanup.

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 AI-generated code before a pull request?▼

Run a separate cleanup pass after implementation finishes. Ask the AI to review all changes for dead code, debug artifacts like print statements, vague variable names, and unnecessary abstractions, then run the test suite to confirm nothing broke.

What is the two-pass implement then clean up pattern?▼

The two-pass pattern separates implementation from cleanup. Pass one focuses only on making the feature work and tests pass. Pass two reviews the changes with fresh eyes to remove sloppy leftovers like commented-out code and debug prints.

When should I run a code cleanup pass?▼

Run a cleanup pass after any implementation touching three or more files, after rapid prototyping, after long debugging sessions that left artifacts, and before creating a pull request. Substantial changes accumulate the most leftover sloppiness.

What kinds of code problems does a cleanup review catch?▼

A cleanup review catches commented-out code, unused imports, console.log and print statements, tests that test the framework instead of your code, abstractions with only one implementation, vague names like temp or data, and catch blocks that just re-throw.

Should cleanup happen in the same prompt as implementation?▼

No. Combining implementation and quality constraints in one pass makes the model satisfy conflicting goals, so neither gets done well. Implement first with full focus on correctness, then clean up in a separate review pass.