remove-ai-slops

Removes AI-generated code slop from branch changes using test-locked parallel cleanup.

Updated Jun 18, 2026
One-click install
npx skills add https://github.com/hugefiver/ocmm --skill remove-ai-slops-hugefiver
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: remove-ai-slops
Source: https://github.com/hugefiver/ocmm/tree/main/plugins/deepwork/skills/remove-ai-slops
Command: npx skills add https://github.com/hugefiver/ocmm --skill remove-ai-slops-hugefiver

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-generated code often accumulates slop: obvious comments, dead code, over-defensive checks, needless abstractions, and oversized modules. Manually cleaning this up risks breaking behavior, and ad-hoc cleanup is unreviewable. This Skill removes slop safely by locking behavior with regression tests before touching a single line. ## Core Features & Use Cases - Behavior Lock First: Writes narrow regression tests to lock observable behavior before any cleanup begins; files without a green baseline are skipped. - 10 Slop Categories: Covers stylistic, structural, hidden-cost, and behavior-coverage issues including dead code, duplication, performance equivalences, and oversized modules over 250 LOC. - Parallel Batch Cleanup: Dispatches up to 5 files concurrently to task agents with per-file category checklists and hard constraints, then verifies with 5 quality gates and 3 review checklists. - Use Case: After merging an AI-assisted feature branch, run the skill to deslop the diff: it scopes changed files via git merge-base, locks behavior, cleans in batches, and reports a final CLEAN or REQUIRES ATTENTION status. ## Quick Start Ask the agent to remove AI slop from the current branch changes and it will lock behavior with tests, clean the files in parallel batches, and verify with quality gates.

Frequently Asked Questions about remove-ai-slops

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I remove AI-generated code slop safely?▼

Lock behavior with regression tests first, then clean in categorized passes. This skill writes narrow tests for each changed file, requires a green baseline before editing, and reverts any hunk that fails the quality gates.

What types of AI code slop can be cleaned automatically?▼

Ten categories are covered: obvious comments, over-defensive code, excessive complexity, needless abstraction, boundary violations, dead code, duplication, performance equivalences, missing tests, and oversized modules over 250 lines.

Does the cleanup change my code's behavior or public API?▼

No. Hard constraints forbid behavior changes, public API signature changes, and new abstractions. Regression tests must stay green, and any failing change is reverted via git checkout and re-applied only if provably safe.

What happens if a file fails the quality gates repeatedly?▼

The failing hunk is reverted and safe changes are re-applied directly, then gates re-run. If the same file fails three times, cleanup stops for that file and the issue is escalated to the user.

When should I not use automated slop removal?▼

Skip it when a change requires algorithmic proof of equivalence, since that is a refactor rather than a slop fix. Also avoid bundling unrelated refactors into a cleanup commit, which makes review and bisection impossible.