skills.rest
HyperionBurn
HyperionBurnCOMMUNITY
Explore all skills by this author →
GitHub

ai-slop-cleaner

Delete dead and redundant logic from AI-generated code with regression tests.

Updated May 5, 2026
Search Tags:#refactoring#regression testing#dead code#deduplication#code cleanup#ai code
One-click install
npx skills add https://github.com/HyperionBurn/searchv1beta --skill ai-slop-cleaner-hyperionburn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ai-slop-cleaner
Source: https://github.com/HyperionBurn/searchv1beta/tree/main/.github/skills/ai-slop-cleaner
Command: npx skills add https://github.com/HyperionBurn/searchv1beta --skill ai-slop-cleaner-hyperionburn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you clean up AI-generated code that works but has unnecessary complexity, duplication, and dead code, while protecting functionality through a regression-safe workflow.

Core Features & Use Cases

  • Deletion-first cleanup: Removes dead code and unused imports before any refactoring, reducing the chance of behavior changes.
  • Regression-safe workflow: Runs a baseline test pass, verifies after each change, and reports what was cleaned and how verification went.
  • Scope-bounded simplification: Targets only the specified files or scope to avoid broad redesign or feature changes.
  • When to use: Ideal for bloated, over-abstracted, duplicated, wrapper-heavy, or unreachable-branch code after an AI-assisted generation.

Quick Start

Clean the specified scope by running the command with optional review mode to identify what would be removed without changing files.

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

To clean up AI-generated code bloat safely, use a deletion-first workflow that removes dead code and unused imports before refactoring, and runs regression tests after each change to verify behavior remains intact.

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

The best way to remove dead code and duplicated logic is through scope-bounded simplification, which targets only specified files to delete redundant wrappers and unreachable branches without causing broad redesigns.

Can I review what code would be removed before making any file changes?▼

Yes, you can run the cleanup in a review-only mode to report findings and identify exactly what dead code or redundant logic would be removed without modifying any files.

How do I safely refactor wrapper layers and unreachable branches across my project?▼

To safely refactor wrapper layers and unreachable branches, execute a baseline test pass first, then apply deletion-first transformations and re-run tests after each change to catch regressions immediately.

Does this code cleanup approach work for targeted refactoring of specific files?▼

Yes, this code cleanup approach works for targeted refactoring by applying scope-bounded simplification to only user-specified files, preventing unintended changes to the broader project behavior.

Related Skills

Explore More Software Engineering Skills→
BerryKuipersBerryKuipers
7

record-quality-baseline

Record code quality metrics before refactoring into a timestamped JSON baseline.

Community
Intermediate
micaelmaltamicaelmalta
1

refactoring

Refactor code incrementally while preserving behavior and passing tests.

Community
Intermediate
DayoptDayopt

cleanup

Detect and remove unused code, dead imports, and console statements in TypeScript/JavaScript projects.

Official
Advanced
aurabxaurabx
3

automatic-refactoring

Apply systematic refactoring techniques to reduce code complexity and technical debt.

Official
Intermediate