deslop

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

Updated May 18, 2025
One-click install
npx skills add https://github.com/nthpaul/dotfiles --skill deslop-nthpaul
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deslop
Source: https://github.com/nthpaul/dotfiles/tree/main/cursor/.cursor/plugins/cache/cursor-public/cursor-team-kit/d1cdb88a9eb33cf392395c87e3fd76419fc1010e/skills/deslop
Command: npx skills add https://github.com/nthpaul/dotfiles --skill deslop-nthpaul

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you clean up AI-generated code by removing unnatural, overly defensive, or style-inconsistent changes that make diffs harder to review and maintain.

Core Features & Use Cases

  • Diff-focused cleanup: Reviews changes versus main to identify AI-introduced “slop” rather than rewriting everything.
  • Style and correctness guardrails: Targets patterns like unnecessary comments, abnormal try/catch or defensive checks, redundant any-casts, and over-nested logic.
  • Behavior-preserving refactors: Improves readability and consistency while keeping functionality unchanged unless a clear bug is fixed.

Quick Start

Ask an AI to review the branch diff against main and remove AI-generated slop while preserving behavior, focusing on comments, defensive checks, any casts, and overly nested logic.

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 TypeScript diff?

To remove AI generated code slop from a TypeScript diff, review the branch changes against main and target unnecessary comments, abnormal try/catch blocks, redundant any casts, and overly nested logic while ensuring behavior preservation.

What is AI code slop in refactoring and code review?

AI code slop in refactoring refers to unnatural style, overly defensive patterns, and inconsistent casting introduced by models in trusted code paths, which damages maintainability and makes diffs harder to review.

How do I clean up defensive code patterns without changing behavior?

Clean up defensive code patterns without changing behavior by applying minimal focused edits to try/catch blocks and excessive nesting, requiring functionality to remain unchanged unless a clear bug is fixed during the style cleanup.

Does behavior-preserving refactoring work with any casts and excessive nesting?

Yes, behavior-preserving refactoring works with any casts and excessive nesting by targeting these specific AI-introduced patterns for removal while keeping functionality unchanged and providing concise change summaries for the reviewed code.

When should I not use AI slop removal during code review?

You should not use AI slop removal when a feature branch contains intentional defensive checks or necessary any casts required for type compatibility, as the process enforces behavior preservation by default and only allows minimal focused edits.