ai-slop-cleaner

Remove duplicate logic, dead code, and needless wrappers from AI-generated code.

Updated May 17, 2026
One-click install
npx skills add https://github.com/tiankong0101-byte/skills-registry --skill ai-slop-cleaner-tiankong0101-byte
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ai-slop-cleaner
Source: https://github.com/tiankong0101-byte/skills-registry/tree/main/skills/oh-my-claudecode/skills/ai-slop-cleaner
Command: npx skills add https://github.com/tiankong0101-byte/skills-registry --skill ai-slop-cleaner-tiankong0101-byte

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps remove AI-generated code slop safely when code works but is bloated, repetitive, over-abstracted, or weakly tested, while preserving intended behavior.

Core Features & Use Cases

  • Regression-safe cleanup: Locks behavior with focused tests before making changes whenever practical.
  • Deletion-first refactoring: Removes dead code, duplicate logic, needless wrappers, and boundary leaks with small, reversible diffs.
  • Reviewer-only mode: Supports a --review pass that inspects cleanup plans, changed files, and verification evidence without editing.
  • Use Case: A module has duplicated helpers, stale branches, and extra abstraction layers after an AI-assisted implementation; this Skill trims the noise and reinforces tests without expanding scope.

Quick Start

Use the ai-slop-cleaner skill to review this code for duplicate logic, dead code, and unnecessary abstraction while keeping behavior unchanged.

Frequently Asked Questions about ai-slop-cleaner

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

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

To clean up AI-generated code slop without changing behavior, you can apply a deletion-first refactoring approach. This method removes dead code, duplicate logic, and needless wrappers while locking intended behavior with focused regression tests.

What is the best way to remove duplicate logic and dead code from an AI-assisted implementation?

Removing duplicate logic and dead code is best handled by bounded refactoring passes that generate small, reversible diffs. This technique trims repetitive helpers and stale branches without expanding the scope of the original implementation.

Can I review cleanup plans for over-abstracted code before applying changes?

Yes, you can use a reviewer-only mode to inspect cleanup plans, changed files, and verification evidence. This review pass analyzes proposed refactoring edits without directly modifying the source code.

How does regression-first verification work during code refactoring?

Regression-first verification locks behavior with focused tests before making any refactoring changes. This testing mechanism ensures that cleanup work on boundary leaks and weak test coverage preserves the original intended behavior.

When do I need a separate review step for high-impact code cleanup?

A separate review step is needed for high-impact code cleanup to safely inspect changes to boundary leaks and weak regression coverage. This precaution ensures scoped file lists and deletion-first edits are verified before merging.