deslop

Remove AI-generated code slop with a regression-safe, deletion-first cleanup workflow.

1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/atmigtnca/sidep-ops --skill deslop-atmigtnca
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deslop
Source: https://github.com/atmigtnca/sidep-ops/tree/main/skills/deslop
Command: npx skills add https://github.com/atmigtnca/sidep-ops --skill deslop-atmigtnca

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clean AI-generated code slop by applying a regression-safe, deletion-first cleanup workflow, preserving behavior while removing unnecessary complexity.

Core Features & Use Cases

  • Enforces a plan-first approach with small, safe edits focused on removing duplication and dead code
  • Supports a reviewer-only pass via --review and a separate writer pass to keep writer/reviewer separation
  • Bounded scope and reuse of existing utilities to minimize risk and preserve regression coverage

Quick Start

Run /deslop on the target files to begin a bounded, regression-safe cleanup, with an optional reviewer pass

Frequently Asked Questions about deslop

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

FAQPage Schema
How do I remove AI-generated code slop without changing behavior?

AI-generated code slop is removed without changing behavior by applying a regression-safe, deletion-first cleanup workflow that prioritizes removing duplication and dead code while preserving existing utilities.

What is the best way to clean up AI-generated codebases safely?

The best way to clean up AI-generated codebases safely is using a bounded scope and plan-first approach, executing small edits that minimize risk and preserve regression coverage throughout the process.

How does reviewer mode work for code cleanup?

Reviewer mode works for code cleanup by enabling a reviewer-only pass to evaluate changes, keeping writer and reviewer separation strict before applying any deletion-first edits to the target files.

Can I run regression testing alongside a deletion-first refactor?

Regression testing is supported alongside a deletion-first refactor through plan-driven verification, ensuring that bounded scope edits and dead code removal do not alter the original software behavior.

When should I not use a bounded scope cleanup workflow?

A bounded scope cleanup workflow should not be used when a codebase requires large architectural additions rather than deletions, as this process specifically enforces removing duplication and dead code over adding new complexity.