A process to remove AI-generated slop from a branch by diff against main.

When should I use deslop?

On explicit request; not in routine implementation discussions.

What should the summary include?

A 1-3 sentence recap of what was changed, focusing on removed slop.

deslop

npx machina-cli add skill gologo13/agent-skills/deslop --openclaw

Files (1)

SKILL.md

750 B

Remove AI code slop

Check the diff against main, and remove all AI generated slop introduced in this branch.

This includes:

Extra comments that a human wouldn't add or is inconsistent with the rest of the file
Extra defensive checks or try/catch blocks that are abnormal for that area of the codebase (especially if called by trusted / validated codepaths)
Casts to any to get around type issues
Any other style that is inconsistent with the file

Report at the end with only a 1-3 sentence summary of what you changed

Source

git clone https://github.com/gologo13/agent-skills/blob/main/skills/deslop/SKILL.mdView on GitHub

Overview

Deslop is a code-cleaning discipline that compares your branch against main to spot and remove AI-generated slop. It targets extra comments, unnecessary defensive checks, casts to any, and other style inconsistencies introduced by automation. Use only on explicit request to keep routine implementations unaffected.

How This Skill Works

The tool diffs the branch with main, identifies AI-generated noise and non-essential blocks, and removes those items while preserving functional code and intent. It ensures the final diff remains focused on meaningful changes. It reports a concise 1-3 sentence summary of what changed at the end.

When to Use It

When a branch includes AI-generated slop such as extra comments or dummy defensive checks.
When the diff against main contains casts to any or other non-essential constructs introduced by automation.
When code style in the branch diverges from project conventions and needs alignment.
When preparing a PR and you want to remove AI noise on explicit request rather than in routine flows.
When auditing a merge to ensure only meaningful logic changes are present.

Quick Start

Step 1: Run the deslop check against main on your feature branch.
Step 2: Remove the AI-generated slop identified (comments, checks, casts).
Step 3: Run tests and commit a 1-3 sentence summary of changes.

Best Practices

Run deslop only on explicit request, not in routine workflows.
Limit the scope to the diff against main to avoid unintended removals.
Preserve functionality; remove only non-essential AI-generated noise.
Review each removal to ensure no necessary logic is stripped.
Follow with full tests and include a brief summary of changes.

Example Use Cases

PR deleting redundant AI-added comments in a service module.
Cleaning up TypeScript code by removing 'cast to any' introduced by an AI helper.
Stripping extra defensive checks in a trusted code path.
Harmonizing inconsistent style across a new feature branch.
Finalizing a hotfix branch by removing AI noise before merge.

Frequently Asked Questions

Add this skill to your agents