dev-ai-slop-cleaner

Remove AI-generated slop patterns from code diffs while preserving behavior.

520|175|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/evolution-foundation/evo-nexus --skill dev-ai-slop-cleaner-evolution-foundation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-ai-slop-cleaner
Source: https://github.com/evolution-foundation/evo-nexus/tree/main/.claude/skills/dev-ai-slop-cleaner
Command: npx skills add https://github.com/evolution-foundation/evo-nexus --skill dev-ai-slop-cleaner-evolution-foundation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes the common “AI slop” patterns that make generated code harder to read, extend, and maintain—so you can quickly get back to clean, purpose-built implementations.

Core Features & Use Cases

  • Single-use helper removal: collapses trivial functions or one-off utilities into direct expressions where appropriate.
  • De-bloat over-abstractions: identifies heavy patterns that add complexity without earning their keep.
  • Fixes generic naming and scope creep: replaces vague function names and strips unrequested configuration knobs.

Use case: After a feature lands via an AI burst, you review the resulting diff and want a targeted cleanup pass that preserves behavior while reducing clutter.

Quick Start

Ask an agent to run dev-ai-slop-cleaner on your latest AI-generated diff after dev-autopilot completes.

Frequently Asked Questions about dev-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 bloat in TypeScript diffs?

Cleaning up AI-generated code bloat involves removing single-use helpers, over-abstractions, and generic naming from TypeScript diffs while preserving the original behavior through a targeted simplification pass.

What are common AI slop patterns in generated code?

Common AI slop patterns include single-use helper functions, unrequested configurability knobs, heavy over-abstractions that add complexity without value, and vague generic naming that obscures the code's actual purpose.

How to refactor AI-generated code without changing behavior?

Refactoring AI-generated code without changing behavior requires scanning diffs for slop signatures, proposing cleaned replacements, applying changes through a designated executor, and verifying behavior with dev-verify to ensure logic remains intact.

When do I need to run a code cleanup pass after AI generation?

A code cleanup pass is needed after a multi-file AI generation burst completes and the resulting diff contains trivial functions, unrequested configuration, or heavy abstractions that reduce overall maintainability.

Does code cleanup remove unrequested configurability from AI diffs?

Yes, code cleanup removes unrequested configurability from AI diffs by identifying and stripping configuration knobs that were added without request, simplifying the implementation down to purpose-built logic.