Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
shipshitdev avatar

De Slop

  • 56 installs
  • 31 repo stars
  • Updated August 2, 2026
  • shipshitdev/library

Helps with ai & agent building tasks.

About

de-slop is a Claude Code skill for ai & agent building. It helps solo builders move faster with AI-assisted development.

  • de-slop
  • AI & Agent Building
  • AI-coding skill

De Slop by the numbers

  • 56 all-time installs (skills.sh)
  • +4 installs in the week ending Aug 5, 2026 (Skillselion tracking)
  • Ranked #6,750 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/shipshitdev/library --skill de-slop

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs56
repo stars31
Last updatedAugust 2, 2026
Repositoryshipshitdev/library

What it does

Helps with ai & agent building tasks.

Files

SKILL.mdMarkdownGitHub ↗

De-Slop

Remove AI-generated artifacts and code sloppiness while maintaining project structure.

What Gets Cleaned

1. Console statements — Replace with logger service 2. `any` types — Replace with proper types/interfaces 3. Unused imports — Remove completely 4. Commented-out code — Remove dead code blocks 5. Temporary/debug code — Remove TODO/FIXME debug statements 6. Obvious AI comments — Remove redundant comments 7. Unused variables — Remove if truly unused 8. Unnecessary defensive checks — Remove try-catch and null guards on trusted internal paths that cannot actually fail; keep guards on real external boundaries 9. Over-nesting — Collapse deep if/else pyramids into early returns, matching the surrounding file's existing style

Workflow

Step 1: Detect Project Structure

Determine if monorepo or single project:

ls packages/ 2>/dev/null || ls pnpm-workspace.yaml 2>/dev/null || true

If monorepo: process each package separately.

Step 2: Identify Artifacts

Search for each artifact type across the codebase.

Step 3: Execute Cleanup (Per Package)

For each package/project:

1. Console statements — Replace with logger 2. any types — Create interfaces, replace types 3. Unused imports — Remove 4. Commented code — Remove blocks 5. Debug code — Remove temporary code 6. Obvious comments — Remove redundant comments 7. Unused variables — Remove

Step 4: Verify

bun run type-check || tsc --noEmit
bun run test

Step 5: Document

Log cleanup in today's session file (.agents/sessions/YYYY-MM-DD.md) with packages cleaned and artifact counts.

Scope

  • Default: clean the current package/project directory
  • To clean across an entire monorepo, explicitly ask for all packages
  • To preview without making changes, ask for a dry run first

Diff-only mode (--changed)

To clean only what the current branch introduced — the safest scope for a PR, and the right default when tidying after AI-assisted work on a branch — restrict edits to the changed lines rather than the whole tree:

BASE="$(git merge-base HEAD origin/HEAD 2>/dev/null || git merge-base HEAD main 2>/dev/null || git merge-base HEAD master)"
git diff --name-only "$BASE"..HEAD           # files this branch touched
git diff "$BASE"..HEAD                         # the exact introduced lines

Only de-slop the files (and ideally the hunks) that appear in that diff. Do not touch pre-existing slop elsewhere in the tree in this mode — that keeps the cleanup reviewable and scoped to your own change. Fall back to whole-tree cleanup only when explicitly asked.

Modes

  • default — clean the current package/project directory and apply the fixes
  • `--changed` — clean only the files/hunks this branch introduced (the diff-only

mode above); the safest scope for a PR

  • `all` — sweep every package in a monorepo, processing each separately
  • `dry-run` — run detection only: report every artifact that would be cleaned,

grouped by type with counts, and make no edits. Combine with any scope, e.g. dry-run over --changed.

Safety Rules

  • Never delete critical files (README, configs, entry points)
  • Respect logger service patterns
  • Be careful with side-effect imports (CSS, polyfills)
  • Keep comments that explain "why", remove comments that restate "what"

Related skills

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.