ai-slop-cleaner

Remove duplicate logic, dead code, and unnecessary wrappers from codebases.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clean AI-generated code slop by applying a regression-safe, deletion-first cleanup that preserves behavior and reduces noise.

Core Features & Use Cases

  • Deletion-first cleanup reduces bloat while maintaining functionality.
  • Regression-safe workflow with focused verification and optional reviewer-only mode.
  • Scoped changes with plan-before-editing and minimal, reversible diffs.

Quick Start

Describe the files to clean and run the AI Slop Cleaner to start a bounded, regression-safe cleanup.

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 without breaking existing functionality?

To clean up AI-generated code safely, apply a regression-safe, deletion-first workflow that preserves behavior. This process targets duplicate logic, dead code, and unnecessary wrappers while keeping tests green.

What is deletion-first code cleanup and when should I use it?

Deletion-first code cleanup reduces bloat by removing dead code and unnecessary wrappers while maintaining functionality. Use it when AI-generated code introduces noise and duplicate logic across your codebase.

How do I review AI code refactoring changes without applying them directly?

You can review AI code refactoring changes without applying them by using an optional reviewer-only mode. This generates a focused cleanup plan with minimal, reversible diffs for inspection.

Can I limit automated code cleanup to specific files and scopes?

Yes, you can limit automated code cleanup to specific files by operating on bounded file scopes. This enforces a plan-before-editing approach that minimizes changes and keeps tests green.

What is the best way to remove dead code and duplicate logic from a codebase?

The best way to remove dead code and duplicate logic is a regression-safe cleanup workflow. It enforces a cleanup plan, minimizes changes, and keeps tests green while remediating unnecessary wrappers.