Deslop

Use this skill for broad code-quality cleanup where the goal is to make the codebase smaller, clearer, more strongly typed, and less defensive or legacy-laden.

Operating Model

Treat this as coordinated research plus implementation, not a blind cleanup sprint.

1. Inspect the repo first: language, package manager, test commands, lint/typecheck commands, dependency graph tooling, and current git status.
2. If a subagent or multi-agent tool is not already visible, search for one before falling back. If subagents are available, dispatch exactly 8 independent subagents, one for each lane below. If subagents are unavailable, run the same lanes sequentially and say so.
3. Give each lane a narrow, evidence-based prompt. Require detailed research, a critical assessment of current code, recommendations with confidence levels, and implementation of only high-confidence recommendations.
4. Integrate the results yourself. Review every diff, reconcile conflicts, and reject speculative or risky changes.
5. Verify with the strongest practical checks: typecheck, lint, targeted tests, dependency analysis, and any affected app build.

The 8 Lanes

1. Deduplication and DRY Find duplicated logic, repeated utilities, copied UI, repeated config, and near-identical workflows. Consolidate only when it reduces complexity or clarifies ownership.