deslop

Identify and remove AI-generated code slop from branch diffs.

2|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/JaimeJunr/context-mode --skill deslop-jaimejunr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deslop
Source: https://github.com/JaimeJunr/context-mode/tree/main/.claude/skills/deslop
Command: npx skills add https://github.com/JaimeJunr/context-mode --skill deslop-jaimejunr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Remove AI-generated code slop introduced in branches by reviewing diffs against main and cleaning up inconsistent patterns.

Core Features & Use Cases

  • Focus on removing unnecessary comments and inconsistent styling to align with project standards
  • Apply defensive checks to ensure behavior remains unchanged
  • Provide guidance for simplifying deeply nested code paths while preserving functionality
  • Use Case: during code review and branch cleanup to restore clean code quality

Quick Start

Review the latest branch diff and remove AI slop while preserving original behavior.

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

To remove AI-generated code slop from a branch diff, compare the branch against main and target unnecessary comments, defensive checks, and casts. This process enforces clean code style while preserving baseline functionality with minimal-change diffs.

Can I clean up inconsistent AI styling across multiple files without breaking functionality?

Yes, you can clean up inconsistent AI styling across multiple files and languages by applying guardrails that preserve behavior and avoid broad rewrites. This ensures baseline functionality remains unchanged while simplifying deeply nested code paths.

Does this refactoring approach work for multiple programming languages?

Yes, this refactoring approach works across multiple programming languages during code review and refactoring workflows. It identifies inconsistent patterns by comparing branch diffs against the main branch to enforce clean code style.

What is the best way to review AI-generated code for unnecessary defensive checks?

The best way to review AI-generated code for unnecessary defensive checks is to compare the branch diff against main and apply guardrails. This targets unnecessary casts and defensive checks while providing a clear, minimal-change diff to preserve behavior.

When should I avoid using automated code cleanup on my branch?

You should avoid automated code cleanup when broad rewrites are required, as this approach targets minimal changes to preserve behavior. If baseline functionality cannot be verified through diff comparison, avoid applying cleanup guardrails.