deslop

Removes AI-generated code slop and over-engineering from branch diffs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-assisted coding often leaves behind unnecessary comments, defensive code, premature abstractions, and unrequested features that bloat pull requests and reduce maintainability. This Skill cleans up that slop before committing. ## Core Features & Use Cases - Diff-Based Cleanup: Analyzes the branch diff against main using git commands to find only the slop introduced in your changes. - Slop Pattern Detection: Targets obvious comments, defensive try/catch blocks, any casts, premature abstractions, deep nesting, and backwards-compatibility hacks. - Behavior Preservation: Verifies changes with tests and re-runs the diff to confirm only slop was removed. - Use Case: After finishing a feature branch with AI assistance, run this Skill before committing to strip boilerplate and over-engineering, leaving a clean, reviewable diff. ## Quick Start Ask the AI to run the deslop skill to clean up the current branch diff before committing.

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 my branch?

Run the deslop skill, which diffs your branch against origin/main, identifies slop patterns like obvious comments and premature abstractions, applies minimal edits, and re-verifies the diff and tests.

What kinds of code slop does this cleanup target?

It targets obvious comments, defensive try/catch in trusted paths, casts to any, premature helpers and factories, deep nesting, backwards-compatibility hacks, and unrequested features or refactors.

When should I run code slop cleanup?

Run it after completing changes and before committing, or whenever code feels over-engineered. It works on the diff between your branch and origin/main.

Does slop cleanup change my code's behavior?

No, the guardrails require behavior to stay unchanged unless fixing a clear bug. The workflow re-runs tests and the diff to confirm only slop was removed.

What are the limitations of automated slop removal?

It only cleans changes present in the branch diff against main, not pre-existing code. Judgment is still needed to distinguish genuine slop from intentional design decisions.