clean-ai-slop

Remove AI-generated comments and unused symbols from the current git diff.

7|Updated May 28, 2026
One-click install
npx skills add https://github.com/zcaceres/skills --skill clean-ai-slop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clean-ai-slop
Source: https://github.com/zcaceres/skills/tree/main/skills/clean-ai-slop
Command: npx skills add https://github.com/zcaceres/skills --skill clean-ai-slop

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill removes the clutter left behind by AI coding assistants, such as redundant tombstone comments, restating-the-code comments, and unused imports, ensuring your codebase remains clean and professional.

Core Features & Use Cases

  • Intelligent Cleanup: Automatically identifies and removes AI-generated noise like tombstone comments, verbose docstrings, and dead internal symbols.
  • Safety-First Verification: Proposes each change for your approval and verifies the integrity of the codebase by running typechecks and tests after application.
  • Use Case: After a long session of AI-assisted coding, use this skill to strip out all the unnecessary comments and unused imports that accumulated during the process, leaving only high-quality, production-ready code.

Quick Start

Invoke the clean-ai-slop skill to scan your current branch and remove all identified AI-generated noise.

Frequently Asked Questions about clean-ai-slop

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

FAQPage Schema
How do I remove redundant AI-generated comments from my codebase?

You can clean up AI-generated noise by running this skill on your current git diff; it identifies tombstone comments and dead internal symbols, proposing each removal for your approval before applying changes.

What is the best way to clean up unused imports after an AI coding session?

The best way to clean up unused imports is invoking this skill on your current branch; it targets only the current git diff to ensure changes are scoped, removing dead internal symbols left by AI coding assistants.

Does removing AI code noise require running typechecks and tests?

Yes, removing AI code noise requires project-specific typecheck and test commands to verify codebase integrity after modifications, ensuring that stripping comments and unused symbols does not break functionality.

Can I scope AI code cleanup to only my recent git diff changes?

Yes, you can scope AI code cleanup to recent changes because this skill operates exclusively on the current git diff, ensuring all comment and unused symbol removal remains intentional and localized.

What types of AI-generated noise does this skill identify?

This skill identifies AI-generated noise including tombstone comments, restating-the-code comments, verbose docstrings, and dead internal symbols that clutter your codebase after AI-assisted coding sessions.

Why should I review proposed code cleanup changes before they are applied?

You should review proposed changes because this safety-first approach verifies codebase integrity by running typechecks and tests after you approve the removal of AI-generated comments and dead symbols.