De-Slop FAQs

Question 1

When should I use the De-Slop skill?

Accepted Answer

You should invoke De-Slop right before committing your changes or opening a Pull Request. It is specifically designed to be the final step in your development workflow to polish your code and remove any internal 'thinking' files or obvious comments generated during the AI coding process.

Question 2

How does De-Slop improve my development workflow?

Accepted Answer

It automates the tedious manual review process of deleting temporary files and cleaning up 'obvious' comments. By presenting findings in a numbered selection list, it allows you to bulk-clean your changes in seconds, resulting in higher-quality PRs and less friction during code reviews.

Question 3

What does the De-Slop skill do?

Accepted Answer

De-Slop is a specialized capability for Claude Code that identifies and removes 'slop'—unnecessary AI-generated artifacts like redundant comments, temporary files (NOTES.md, SCRATCH.md), bloated docstrings, and generic AI TODOs. It helps ensure your codebase stays professional and free of AI-generated noise.

Question 4

Will De-Slop automatically modify my code without permission?

Accepted Answer

No. Safety is a core feature. De-Slop always performs a dry run first, scanning your changed files and presenting a numbered list of issues. You have full control to select which items to delete, simplify, or ignore. It also flags complex issues like 'mock-heavy tests' for manual verification rather than auto-fixing them.

Question 5

What specific capabilities does De-Slop provide?

Accepted Answer

Its capabilities include scanning for redundant comments that restate obvious code, detecting generic AI-generated TODOs, cleaning up temporary markdown files, simplifying excessive docstrings for trivial functions, and flagging uncited claims or suspicious metrics for manual review.

De-Slop

De-Slop

About

Key Features

Use Cases

About

Key Features

Use Cases