Menu
Remove AI-generated code slop introduced on the current branch and align it with the surrounding codebase.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
| name | ds-deslop |
| description | Remove AI-generated code slop introduced on the current branch and align it with the surrounding codebase. |
| disable-model-invocation | true |
When invoked, diff the current branch against the main branch and remove the slop the branch introduced. Preserve behavior.
The test for slop is simple: code an experienced engineer working in this language and this codebase wouldn't have written. Judge against the surrounding code and the language's idioms — not a fixed checklist.
Treat any argument as scope (files or directories). With no scope, review the branch's diff against the main branch.
try/catch, an if err != nil that can't fire, an unwrap_or masking a real invariant, a null check on a value that's never null.any / as / @ts-ignore in TypeScript or # type: ignore in Python are usually slop; any / interface{} in Go is often idiomatic. Flag the ones that exist only to silence a type error, not the idiomatic uses.? in Rust, match, and so on).Apply the edits, then give a concise 1–3 sentence summary of what was removed or simplified.
Design a target architecture for a new system — module boundaries, dependency rules, seams, and build order — from its requirements. Reports a blueprint; changes nothing.
Analyze an existing codebase's architecture and produce a sequenced refactoring plan — assess module boundaries, dependency structure, and layering, then lay out ordered, risk-tagged steps. Language-agnostic. Reports a plan; changes nothing.
Turn a goal or another command's output into an ordered task roadmap.
Find the root cause of a failure with the scientific method — reproduce, isolate, fix, then prove it.
Interview the user relentlessly about a plan or design until reaching shared understanding.
Run an extremely strict maintainability + single-source-of-truth review of code changes — abstraction quality, file sprawl, spaghetti-condition growth, and duplicate/competing implementations. Reports findings by default; `--fix` applies the mechanical, unambiguous ones — structural/code-judo restructurings rest on judgment and stay reported.