ai-slop-cleaner

AI-generated code cleanup requires a regression tests-first approach to ensure behavior preservation. This skill systematically identifies code smells like duplication and dead code, then refactors them while running tests, linters, and static analysis to verify behavior remains unchanged throughout the process.

Smell-by-smell refactoring is the best approach for redundant abstractions in AI-generated code. By targeting specific code smells individually—such as unnecessary abstractions, dead code, and duplication—you can methodically clean up bloated code while maintaining strict regression test coverage to preserve original behavior.

You can perform scoped code cleanup on specific files or broader feature areas rather than processing the whole project. This targeted approach allows precise desloping of AI-generated code sections while maintaining behavior preservation through regression tests and quality gate checks on the selected scope.

Quality gate integration for refactoring AI code works by enforcing tests, linters, and static analysis checks throughout the cleanup process. This mechanism ensures that each refactoring step passes code quality standards before proceeding, preventing regressions and systematically removing AI-generated slop while maintaining structural integrity.

An automated AI code cleanup workflow should be used when dealing with large volumes of AI-generated code containing systematic smells like duplication, dead code, and unnecessary abstraction. Its regression test-first approach ensures behavior preservation, making it ideal for AI development pipelines where manual refactoring would be inefficient.

Yes, existing test coverage is required before running an anti-slop cleanup because the workflow is regression tests-first. These tests verify behavior preservation during smell-by-smell refactoring, ensuring that removing dead code, duplication, and unnecessary abstractions does not alter the original functionality.