# Deslop

Remove AI-generated code slop, unnecessary comments, and over-engineering from the...

- Repository: https://github.com/rohitg00/pro-workflow (2940 stars)
- Category: Engineering
- License: see repository
- Last updated: 2026-09-29
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add rohitg00/pro-workflow --skill deslop -g -a claude-code -y`
Codex: `npx skills add rohitg00/pro-workflow --skill deslop -g -a codex -y`
Cursor: `npx skills add rohitg00/pro-workflow --skill deslop -g -a cursor -y`
Gemini CLI: `npx skills add rohitg00/pro-workflow --skill deslop -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add rohitg00/pro-workflow`

## Description

Remove AI-generated code slop, unnecessary comments, and over-engineering from the current branch diff. Cleans up boilerplate, simplifies abstractions, strips defensive code, and in skill-file mode lints SKILL.md files for quality. Use when cleaning up code, simplifying, removing boilerplate, before committing, or when reviewing a skill before promoting it.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Remove AI Code Slop

Check the diff against main and remove AI-generated slop introduced in the branch.

## Trigger

Use after completing changes, before committing, or when code feels over-engineered.

## Commands

```bash
git fetch origin main
git diff origin/main...HEAD --stat
git diff origin/main...HEAD
```

## Workflow

1. Run diff commands to see all changes on the branch.
2. Identify slop patterns from the focus areas below.
3. Apply minimal, focused edits to remove slop.
4. Re-run `git diff origin/main...HEAD` to verify only slop was removed.
5. Run tests or type-check to confirm behaviour unchanged: `npm test -- --changed --passWithNoTests 2>&1 | tail -10`
6. Summarise what was cleaned.

## Focus Areas

- Extra comments that state the obvious or are inconsistent with local style
- Defensive try/catch blocks that are abnormal for trusted internal code paths
- Casts to `any` used only to bypass type issues
- Over-engineered abstractions for one-time operations (premature helpers, factories)
- Deeply nested code that should be simplified with early returns
- Backwards-compatibility hacks (renamed `_vars`, re-exports, `// removed` comments)
- Features, refactoring, or "improvements" beyond what was requested
- Added docstrings, type annotations, or comments on code that wasn't changed
- Error handling for scenarios that can't happen in trusted internal paths

## Guardrails

- Keep behavior unchanged unless fixing a clear bug.
- Prefer minimal, focused edits over broad rewrites.
- Three similar lines of code is better than a premature abstraction.
- If you remove something, verify it's truly unused first.
- Keep the final summary concise (1-3 sentences).

## Skill-file mode

When the target is a `SKILL.md` (not a code diff), lint it against the same
slop instinct applied to prose. Run this before promoting a skill. Flag:

The rest: https://github.com/rohitg00/pro-workflow/blob/HEAD/skills/deslop/SKILL.md