de-sloppify

Enforce a two-pass development workflow separating implementation from cleanup.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/kitfunso/omniskill --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/omniskill/tree/main/skills/de-sloppify
Command: npx skills add https://github.com/kitfunso/omniskill --skill de-sloppify-kitfunso

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Two-pass development enforces separating feature implementation from cleanup tasks to prevent lingering cruft and suboptimal design after large changes.

Core Features & Use Cases

  • Enforces a two-pass workflow: implement first, then clean up in a separate pass to improve maintainability.
  • Reduces code churn by surfacing cleanup opportunities during the second pass and standardizing naming, error handling, and dead code removal.
  • Use Case: after implementing a major feature, run the de-sloppify process to deliver a cleaner, more robust codebase ready for PR review.

Quick Start

After implementing a feature, perform a second pass to de-sloppify: remove dead code, debug artifacts, and simplify abstractions.

Frequently Asked Questions about de-sloppify

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

FAQPage Schema
What is two-pass development for code cleanup?

Two-pass development is a workflow pattern that separates feature implementation from cleanup. Pass 1 implements functionality and Pass 2 performs code cleanup to reduce code smell, remove dead code, and simplify abstractions.

How do I reduce code churn after implementing a major feature?

To reduce code churn after a major feature, perform a second de-sloppify pass. This cleanup phase surfaces opportunities to standardize naming, improve error handling, and remove debug artifacts before finalizing the codebase.

When do I need to run a separate cleanup pass on my codebase?

You need a separate cleanup pass when completing major feature work, large refactors, or substantial code changes. This ensures consistent quality by removing dead code and simplifying abstractions before PR review.

Can I use two-pass refactoring for small code changes?

Two-pass refactoring is designed for major feature work, large refactors, and substantial code changes. For minor modifications, a separate cleanup pass to remove dead code and debug artifacts may be unnecessary overhead.

What does a de-sloppify code cleanup pass remove?

A de-sloppify cleanup pass removes dead code, debug artifacts, and suboptimal abstractions. It standardizes naming and error handling to deliver a cleaner, more maintainable codebase ready for review.

Why separate feature implementation from code cleanup?

Separating implementation from cleanup prevents lingering cruft and suboptimal design after large changes. This two-pass approach reduces code churn and ensures consistent quality across the codebase.