ai-slop-cleaner

To remove AI-generated code slop safely, you need a regression-safe workflow that deletes redundant wrappers and dead code while running tests afterwards to verify behavior is preserved. This skill implements exactly that process within a defined scope.

The best way to clean up over-abstracted helpers and duplicated logic is to apply targeted code simplification within explicit boundaries, collapsing redundant structures into a lean codebase while verifying tests pass after deletions.

Yes, the workflow applies to any language project where bloated wrappers, duplicated logic, or over-abstracted helpers exist, as long as you define the scope and have tests in place for regression verification.

Yes, the slop cleaner supports a review mode for non-destructive analysis, allowing you to identify over-abstraction and dead code before making any actual deletions to your codebase.

You should run regression testing after removing dead code because deletions can cause unexpected behavior changes; verifying tests pass afterwards ensures the cleanup preserved existing functionality without introducing regressions.