deslop

Remove noise from nearly finished code changes before commit.

434|33|Updated Jul 27, 2025
One-click install
npx skills add https://github.com/udecode/kitcn --skill deslop-udecode
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: deslop
Source: https://github.com/udecode/kitcn/tree/main/.agents/skills/deslop
Command: npx skills add https://github.com/udecode/kitcn --skill deslop-udecode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deslop helps remove noise from a nearly finished change, providing a bounded final pass before commit or push.

Core Features & Use Cases

  • Bounded helper inside the normal execution lane, not a competing end-to-end workflow.
  • Default scope is changed files only. Do not widen to the whole repo unless the user asks.
  • Prefer deleting or inlining over introducing fresh abstraction.
  • Treat slop-scan as signal, not law. Fix the good hits. Ignore the fake ones.

Quick Start

Run deslop after the implementation works and before committing or pushing to strip noise from an otherwise correct diff.

Frequently Asked Questions about deslop

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

FAQPage Schema
How do I reduce noise in a code diff before committing?▼

Reduce diff noise by running a bounded final cleanup pass on changed files only, preferring to delete or inline code rather than introducing new abstractions.

What is a slop-scan delta and how is it used for diff cleanup?▼

A slop-scan delta is a signal used during diff cleanup to identify noisy code, treated as a signal rather than law, fixing the good hits and ignoring the fake ones.

When should I run a final deslop pass on my code changes?▼

Run a final deslop pass after your implementation works and before committing or pushing, acting as a bounded helper to strip noise from an otherwise correct diff.

Should I clean up the whole repository or just changed files during diff cleanup?▼

During diff cleanup, you should default to changed files only, avoiding widening the scope to the whole repository unless explicitly requested, preventing unnecessary refactoring.

Does running a noise reduction pass require refactoring my entire codebase?▼

No, noise reduction does not require refactoring your entire codebase; it is a bounded helper within the normal execution lane that focuses exclusively on changed files.