Skip to content
Automation
Skill

/deslop

Remove AI-generated code slop from a branch: unnecessary comments, redundant defensive checks, boilerplate, style drift, and type casts. Use for cleanup of AI-written code, not for broad code review, security audit, TDD, or final verification.

From plugin
vibe-skills
2.7k200 skills8 agents3 commands
Install
$ npx -y skills add foryourhealth111-pixel/Vibe-Skills --skill deslop --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/deslop

Context preview

The summary Claude sees to decide when to auto-load this skill.

Remove AI-generated code slop from a branch: unnecessary comments, redundant defensive checks, boilerplate, style drift, and type casts. Use for cleanup of AI-written code, not for broad code review, security audit, TDD, or final verification.

SKILL.md

deslop.SKILL.md
name: deslop
description: Remove AI-generated code slop from a branch: unnecessary comments, redundant defensive checks, boilerplate, style drift, and type casts. Use for cleanup of AI-written code, not for broad code review, security audit, TDD, or final verification.

Remove AI Code Slop

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

Routing Boundary

Use this skill when the user's problem is cleanup of AI-generated code noise. If the user asks for a broad correctness/maintainability review, use `code-reviewer`. If the user asks whether existing review comments should be accepted, use `receiving-code-review`.

What to Remove

  • Extra comments that a human wouldn't add or are inconsistent with the rest of the file
  • Extra defensive checks or try/catch blocks that are abnormal for that area of the codebase (especially if called by trusted/validated codepaths)
  • Casts to `any` to get around type issues
  • Inline imports in Python (move to top of file with other imports)
  • Any other style that is inconsistent with the file

Process

1. Get the diff against main: `git diff main...HEAD` 2. Review each changed file for slop patterns 3. Remove identified slop while preserving legitimate changes 4. Report a 1-3 sentence summary of what was changed

Ships withvibe-skills

VibeSkills is a general-purpose Skill that automatically routes local Skills and intelligently orchestrates harness workflows.

Get the whole plugin

Other skills on vibe-skills.