antislop-code

Removes generic AI-style comments from code while preserving informative ones.

Updated Dec 15, 2025
One-click install
npx skills add https://github.com/zeeforc/website-lpkpaiton --skill antislop-code-zeeforc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: antislop-code
Source: https://github.com/zeeforc/website-lpkpaiton/tree/main/agent/skills/antislop-code
Command: npx skills add https://github.com/zeeforc/website-lpkpaiton --skill antislop-code-zeeforc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI coding agents often fill code with generic, decorative comments—banner separators, step-by-step narration, restated signatures, and vague TODOs—that add noise without information. This Skill defines rules to strip that slop while protecting comments that carry real meaning. ## Core Features & Use Cases - Slop Comment Detection: Identifies decorative separators, obvious restatements, workflow narration, empty labels, vague TODOs, signature echoes, decorative emoji, and end markers. - Preservation Rules: Explicitly protects comments explaining business logic, security, performance trade-offs, API contracts, workarounds, and edge cases. - Scope Guardrail: Modifies comments only—never touches executable code, identifiers, formatting, or logic. - Use Case: After an AI agent generates a module full of // Step 1: Validate input and // ===== ROUTES ===== comments, run this Skill to clean the file down to only the comments that explain non-obvious behavior. ## Quick Start Clean the AI-generated comments in this file, removing decorative and redundant ones while keeping any comment that explains why the code works the way it does.

Frequently Asked Questions about antislop-code

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

FAQPage Schema
How do I remove AI-generated slop comments from code?▼

Apply the antislop comment rules: delete decorative separators, restated obvious lines, step-by-step narration, empty labels, vague TODOs, signature echoes, decorative emoji, and end markers. Keep only comments that explain why the code behaves the way it does.

What kinds of code comments should be kept during cleanup?▼

Keep comments explaining business logic, architectural decisions, security considerations, performance trade-offs, concurrency behavior, protocol details, API contracts, workarounds, edge cases, and licensing notices. These carry information the code itself does not show.

Does cleaning comments risk changing the code behavior?▼

No. The Skill enforces a strict scope guardrail: only comments are modified. Executable code, identifiers, imports, formatting, indentation, whitespace, control flow, and logic must remain untouched.

When should a TODO comment be kept or removed?▼

Remove vague TODOs like "improve this" or "add more validation" because they name a feeling, not a task. Keep a TODO only when it names a specific, actionable task with enough context to act on.

What are the limitations of automated comment cleanup?▼

The rules rely on judgment about whether a comment adds real information, so borderline cases need human review. It also depends on the companion antislop core rules and does not fix structural code problems that excessive narration may hide.