ai-slop-cleaner

Remove dead code and duplicate logic from target modules while preserving behavior.

5|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/RobinNorberg/oh-my-copilot --skill ai-slop-cleaner-robinnorberg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ai-slop-cleaner
Source: https://github.com/RobinNorberg/oh-my-copilot/tree/main/skills/ai-slop-cleaner
Command: npx skills add https://github.com/RobinNorberg/oh-my-copilot --skill ai-slop-cleaner-robinnorberg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

AI-generated code often includes unnecessary wrappers, dead branches, and bloated abstractions that increase maintenance burden. This skill provides a disciplined, test-first approach to delete extraneous code while preserving behavior.

Core Features & Use Cases

  • Systematic deletion-first cleanup to remove dead code, duplicate logic, and unnecessary wrappers.
  • Optional reviewer-only mode to validate changes before final application.
  • Structured workflow with plan, write, and verify steps to lock behavior with tests.

Quick Start

Describe the code to be cleaned and run an AI-guided slop cleanup with an optional reviewer pass.

Frequently Asked Questions about ai-slop-cleaner

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

FAQPage Schema
How do I remove dead code and duplicate logic from AI-generated modules?

To remove dead code and duplicate logic, this skill applies a systematic deletion-first cleanup approach that strips unnecessary wrappers and bloated abstractions while preserving original behavior.

What is the best way to clean up bloated AI code without breaking existing behavior?

The best way to clean up AI code without breaking behavior is using a test-first cleanup approach that locks behavior with existing tests and regression coverage before finalizing changes.

Can I review code cleanup changes before they are applied to my project?

Yes, you can validate changes before final application by using the optional reviewer-only mode to inspect the proposed cleanup of dead branches and wrappers before committing.

Do I need existing tests to refactor and deslop my codebase?

Yes, existing tests are required to lock behavior and ensure regression coverage before finalizing any cleanup, as the workflow follows a test-first approach to validate changes.

How does a test-first code cleanup workflow verify changes?

A test-first code cleanup workflow verifies changes through structured plan, write, and verify steps that ensure behavior is locked by existing tests and regression coverage before finalizing.