deslop

Remove AI-generated code slop from feature branch diffs against main.

Updated May 22, 2026
One-click install
npx skills add https://github.com/paulbrittain/claude-team-kit --skill deslop-paulbrittain
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deslop
Source: https://github.com/paulbrittain/claude-team-kit/tree/main/skills/deslop
Command: npx skills add https://github.com/paulbrittain/claude-team-kit --skill deslop-paulbrittain

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

AI-generated changes often include unnecessary, inconsistent, or overly defensive code patterns that add noise and reduce maintainability, even when the logic is mostly correct.

Core Features & Use Cases

  • Diff Cleanup Against Main: Reviews the branch changes against main to remove AI-introduced slop while preserving intent.
  • Style- and Structure-Focused Simplification: Targets inconsistent comments, abnormal try/catch patterns, unnecessary deep nesting (via early returns), and type-hack casts like any used only to bypass type issues.
  • Behavior-Preserving Guardrails: Keeps behavior unchanged unless fixing a clear bug, with minimal, focused edits suitable for codebases that value readability and consistency.

Quick Start

Use the deslop skill on the current branch diff by telling the AI: “Clean up the AI-generated slop in my PR while keeping behavior unchanged.”

Frequently Asked Questions about deslop

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I remove AI-generated code slop from a pull request diff?

To remove AI-generated code slop from a pull request, use a diff cleanup tool against the main branch to strip unnecessary comments, defensive constructs, and avoidable `any` type casts while preserving behavior.

What is AI code slop and how does it affect maintainability?

AI code slop consists of unnecessary comments, overly defensive try/catch blocks, and type casts that add noise and reduce maintainability. It complicates diffs with patterns inconsistent with the surrounding codebase without changing logic.

How do I clean up inconsistent code style in a feature branch without breaking logic?

To clean up inconsistent code style safely, apply behavior-preserving edits that simplify deep nesting via early returns and remove abnormal try/catch patterns, ensuring minimal focused changes that do not alter the original intent.

Can I remove unnecessary defensive constructs and `any` casts without changing behavior?

Yes, you can remove unnecessary defensive constructs and `any` type casts through behavior-preserving guardrails. The cleanup applies minimal, focused edits guided by existing codebase patterns to ensure functionality remains unchanged.

Does code cleanup work directly on branch diffs comparing against main?

Yes, diff cleanup works directly by comparing your feature branch changes against main. It reviews the diff to identify and remove AI-introduced slop, applying minimal edits suitable for codebases that value readability.

When should I avoid automated code style cleanup on my pull request?

You should avoid automated code style cleanup if your pull request requires active bug fixing rather than behavior-preserving edits, as the cleanup tool focuses solely on removing slop and inconsistent style without altering logic.