Adapted from cursor/plugins, cursor-team-kit/skills/deslop/SKILL.md, at commit 93b00b89ef425a9c1bac0d0b317dfc49c930ac99 (MIT, Copyright (c) 2026 Cursor). Subtraction-first, caller-migration, legacy-deletion, and behavior-pin principles are additionally adapted from pstack/skills/poteto-mode at the same commit.

Use for an explicit broad codebase cleanup request, or when the model offers a cleanup pass at a commit or PR boundary. Do not run it automatically on every edit.

Deslop code safely

Make the requested scope materially smaller and easier to understand without changing its supported behavior.

Resolve the scope

1. Treat every supplied target as a scope item. Accept repository roots, directories, package/module names, and files.
2. Resolve paths relative to the current working directory. Resolve module names through the project's language conventions and code search.
3. If no target is supplied, use the current Git repository root, or the current directory when outside Git.
4. If a target is missing or resolves to multiple places, ask the user before editing.
5. Inspect callers, dependents, tests, configuration, entry points, and documentation outside the scope when needed to prove safety. Keep production edits inside the requested scope unless a directly dependent file must change to preserve correctness. Explain any necessary scope expansion.
6. Exclude vendored dependencies, generated output, caches, build artifacts, and user-owned untracked files unless the user explicitly includes them.

Establish evidence first