ai-slop-cleaner

Remove duplication, dead code, and stale branches while preserving behavior.

3|Updated May 24, 2026
One-click install
npx skills add https://github.com/shayne-snap/oh-my-antigravity --skill ai-slop-cleaner-shayne-snap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ai-slop-cleaner
Source: https://github.com/shayne-snap/oh-my-antigravity/tree/main/plugin/skills/ai-slop-cleaner
Command: npx skills add https://github.com/shayne-snap/oh-my-antigravity --skill ai-slop-cleaner-shayne-snap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes accumulated “slop” in a codebase—duplication, dead code, stale branches, and boundary violations—while keeping behavior unchanged through evidence-first cleanup.

Core Features & Use Cases

  • Scope-bounded cleanup: Uses an explicit user scope or (when Ralph state is active) deslop_changed_files_path to prevent accidental expansion into unrelated files.
  • Behavior-preserving refactor discipline: Locks behavior to existing regression coverage and strengthens tests before making changes when coverage is weak.
  • Ralph-integrated verification: When used in Ralph’s mandatory deslop pass, it records cleanup status and reruns focused verification (tests/build/lint/typecheck as applicable).
  • Evidence-dense reporting: Produces an “AI SLOP CLEANUP REPORT” that lists smells removed, verification results, and residual risks.

Quick Start

Use this skill when you want a behavior-preserving cleanup of the current project scope after planning or during Ralph’s cleanup pass by telling the assistant: “Run /omagy:ai-slop-cleaner on my current change scope and verify with targeted regression checks.”

Frequently Asked Questions about ai-slop-cleaner

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

FAQPage Schema
How do I safely remove dead code and duplication without changing program behavior?

Behavior-preserving code cleanup locks refactoring to existing or added regression coverage, removing slop like dead code and duplication while running targeted verification to prove functionality remains unchanged.

What is the best way to refactor a codebase while ensuring test coverage is maintained?

Behavior-preserving refactor discipline strengthens weak regression coverage before making changes, avoiding dependency updates and unrelated rewrites to ensure the original behavior remains intact.

How do I clean up accumulated code slop in a specific file or diff scope?

Scope-bounded cleanup uses an explicit user scope or deslop_changed_files_path to prevent accidental expansion into unrelated files, ensuring only targeted duplication and dead code are removed.

Does behavior-preserving code cleanup work with Ralph state management?

Ralph-integrated verification records cleanup status and reruns focused verification checks, including tests, build, lint, and typecheck, when used during Ralph's mandatory deslop pass.

What are the limitations of automated dead-code removal and stale branch cleanup?

Limitations of automated dead-code removal include avoiding dependency changes and unrelated rewrites, requiring existing regression coverage to lock behavior, and handling noop scenarios when the cleanup scope is empty.