ai-slop-cleaner

Clean AI-generated code slop with regression-safe, deletion-first passes.

Updated Mar 17, 2026
One-click install
npx skills add https://github.com/Rheinmir/skills-kit --skill ai-slop-cleaner-rheinmir
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ai-slop-cleaner
Source: https://github.com/Rheinmir/skills-kit/tree/main/skills/ai-slop-cleaner
Command: npx skills add https://github.com/Rheinmir/skills-kit --skill ai-slop-cleaner-rheinmir

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clean AI-generated code slop without drifting scope or changing intended behavior, using a regression-safe, deletion-first workflow.

Core Features & Use Cases

  • Bounded cleanup passes that target bloated code, duplicated logic, weak tests, and over-abstracted wrappers.
  • Supports reviewer-only anti-slop mode via flags and provides a clear cleanup plan aligned with existing utilities and patterns.
  • Ensures changes are small, reversible, and verified by regression tests before application.

Quick Start

Provide a bounded anti-slop cleanup on the target files and start with a regression-test 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 safely clean up AI-generated code slop without changing behavior?

AI code slop cleanup preserves intended behavior by enforcing a bounded, deletion-first workflow. It requires a cleanup plan, reuses existing utilities, and verifies all changes with focused regression tests before application to prevent scope drift.

What is the best way to remove duplicated logic and over-abstracted wrappers from AI code?

The best way to remove duplicated logic and over-abstracted wrappers is running bounded cleanup passes on working-but-bloated code. This targets weak tests and dead code while keeping diffs small and reversible for safe refactoring.

Can I run a reviewer-only anti-slop pass on existing code?

Yes, you can run a reviewer-only anti-slop pass by using specific flags. This mode generates a clear cleanup plan aligned with existing utilities and patterns without immediately applying changes, ensuring modifications remain reversible and controlled.

Does this anti-slop cleanup workflow require existing regression tests?

Yes, the anti-slop cleanup workflow requires existing regression tests. It starts with a regression-test pass to verify behavior, ensuring that any deletion of dead code or wrapper layers is validated by focused tests before application.

When should I avoid using a bounded cleanup pass for refactoring?

You should avoid using a bounded cleanup pass when you explicitly intend to change application behavior or need large scope expansions. This workflow is designed strictly for working-but-bloated code, prioritizing small, reversible diffs and deletion over addition.