deslop

Remove AI-generated commentary and dead code from git diffs.

1|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/chrisliu298/dotfiles --skill deslop-chrisliu298
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deslop
Source: https://github.com/chrisliu298/dotfiles/tree/main/agents/extensions/skills/deslop
Command: npx skills add https://github.com/chrisliu298/dotfiles --skill deslop-chrisliu298

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Remove AI-generated slop from code changes by analyzing the diff against main and surgically removing non-essential commentary, dead code, and style inconsistencies while preserving all features and logic.

Core Features & Use Cases

  • Remove AI-generated slop from diffs without altering functionality.
  • Apply to Claude Code and Codex workflows to keep diffs concise across languages.
  • Use during code review and PR prep to produce cleaner, review-friendly changes.

Quick Start

Run the deslop skill after finishing an AI-assisted coding session to tidy the diff.

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 slop from code diffs without breaking functionality?

You can use this Skill directly after an AI-assisted coding session by running it against your current changes. It uses git diff --cached, git diff, or git diff main..HEAD to identify and tidy AI-generated slop in your code.

What is AI-generated slop in a git diff?

AI-generated slop in a git diff refers to non-essential commentary, dead code, and style inconsistencies introduced by AI coding tools. It is identified by analyzing changes against the main branch and surgically removed without altering functionality.

Does this diff cleanup approach work with Claude Code and Codex workflows?

Yes, this diff cleanup approach applies to Claude Code and Codex workflows. It analyzes git changes to keep diffs concise across multi-language projects by stripping non-essential AI commentary and style inconsistencies.

When should I clean up AI slop before creating a pull request?

You should clean up AI slop during code review and PR prep to produce cleaner, review-friendly changes. Running a cleanup pass after finishing an AI-assisted coding session ensures the final diff is concise.

Can I tidy multi-language project diffs with a single git diff cleanup tool?

Yes, you can tidy multi-language project diffs using a tool that analyzes git diff main..HEAD. It identifies AI-generated style inconsistencies and dead code across different languages while preserving features.