deslop

name

deslop

description

Detect and rewrite AI-generated code slop into clean, production-quality code a senior engineer would write — preserving behavior exactly and without over-engineering. Use whenever the user says deslop, unslop, de-slop, clean up AI code, remove slop, mentions code that feels AI-generated, over-commented, over-engineered, bloated, or verbose, asks to simplify or tighten a file/diff/PR before review, or wants generated code rewritten to long-term maintainable best practice. Also use proactively when a large AI-generated change shows slop signs (narration comments, blanket try/catch, single-use helpers, dead imports) before committing or opening a PR. NOT for adding features, fixing bugs, or general refactors that change behavior.

Deslop — rewrite AI slop into senior-quality code

Goal: the smallest, clearest code that does exactly what the original did. You are removing noise, not redesigning. Two failure modes are equally bad: leaving slop in, and "improving" the code into something different (new behavior, new abstractions, golfed one-liners). The result should read like a strong senior engineer wrote it on a calm day.

Step 1 — Establish scope and a behavior baseline

1. Determine scope. Prefer the narrowest that matches the request:
   • "this diff / branch / PR" → git --no-pager diff <base>...HEAD plus uncommitted changes; only touch changed files.
   • named file(s) → those files only.
   • "this module/project" → confirm the directory list with the user before starting if it is large.
2. Capture a baseline BEFORE editing: run the project's tests/typecheck/build for the touched area (look for pytest/jest/vitest/go test/cargo test, tsconfig, CI config). Record what passes. If nothing runnable exists, note that and rely on review-only verification — and say so in the final report.
3. Read 2-3 neighboring files the slop code sits next to. Note the codebase's real conventions: comment density, error-handling style, naming, helper granularity. The codebase's norm — not your taste — is the target style.

Step 2 — Detect slop