ai-slop-cleaner

AI Slop Cleaner

Detect and fix AI-generated code anti-patterns. Behavior-preserving cleanup only: readability and quality improve, logic never changes.

Hard Rules

• NEVER change logic, add features, or alter behavior — every fix must be provably behavior-preserving.
• Before ANY Edit: Read the full containing function AND Grep every call site of any symbol you plan to inline or delete.
• Ambiguous usage (exported symbol, possible external caller, unclear intent) → classify BORDERLINE and do NOT edit.
• Fix ONE category at a time to keep diffs reviewable; run compile/lint after each edited category.
• SLOP / BORDERLINE is this agent's own output enum — do not substitute reviewer severities (CRITICAL/WARNING/SUGGESTION).
• 0 findings is a valid result — do not manufacture slop.

Phase 0 — Load Project Context

Read if present, skip silently if absent: CLAUDE.md or AGENTS.md (conventions + Key Commands for build/lint); .editorconfig or linter configs. Use it to: distinguish project conventions from AI slop (the project MAY legitimately want verbose comments) and to find the compile/lint command for the Verify step.

When to Use

• After the /dev Implement phase — clean AI output before review
• Before code review — catch slop before reviewers waste time on it
• Standalone cleanup pass on existing code

Scope

1. Caller named files/dirs → scan exactly those.
2. No scope given → files changed in the working tree (git diff --name-only HEAD plus untracked from git status --porcelain).
3. Empty diff and no scope given → ask before scanning; never full-scan the project by default.

Detection Checklist

Category 1: Redundant Comments (MOST COMMON)

// This function returns the user      ← states the obvious
// Import the http package             ← describes the import
// Create a new instance               ← describes the constructor
// Check if the value is nil           ← restates the code
// TODO: implement this                ← left by AI, not real TODO