antislop-code

Removes generic AI-style code comments while preserving informative ones without touching executable code.

Updated Jul 2, 2026
One-click install
npx skills add https://github.com/daxrpm/epn-tracker --skill antislop-code-daxrpm
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: antislop-code
Source: https://github.com/daxrpm/epn-tracker/tree/main/.claude/skills/antislop-code
Command: npx skills add https://github.com/daxrpm/epn-tracker --skill antislop-code-daxrpm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI coding agents tend to leave behind generic, decorative comments—banner separators, step-by-step narration, restated signatures, vague TODOs—that add noise without information. This Skill gives agents a concrete rulebook for cleaning up those comments while protecting the ones that carry real meaning. ## Core Features & Use Cases - Slop Pattern Detection: Identifies decorative separators, restated-obvious comments, workflow narration, empty labels, vague TODOs, signature echoes, decorative emoji, and end markers, each with a Tell/Why/Fix entry tied to a core rule number. - Preservation Guardrails: Explicitly protects comments explaining business logic, security, performance trade-offs, concurrency, API contracts, workarounds, and edge cases. - Scope Guardrail: Modifies comments only—never executable code, identifiers, imports, formatting, or control flow. - Use Case: After an AI agent generates a module full of // Step 1: Validate input and // ===== ROUTES ===== comments, run this Skill to strip the noise and keep only the comments explaining non-obvious behavior. ## Quick Start Review the comments in this file, remove the generic AI-slop ones, and keep only comments that explain something the code does not already show.

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 Tell/Why/Fix patterns: 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 something the code does not already show.

What kinds of code comments should never be removed?▼

Never remove comments explaining business logic, architectural decisions, security considerations, performance trade-offs, concurrency behavior, protocol details, API contracts, workarounds, edge cases, or licensing notices. A comment earns its place when it states something the code cannot show.

Does cleaning up comments risk changing the code behavior?▼

No. The Skill enforces a strict scope guardrail: only comments may be modified. Executable code, identifiers, imports, formatting, indentation, whitespace, and control flow must remain untouched, so behavior cannot change.

When should a TODO comment be kept versus deleted?▼

Keep a TODO only when it names a specific, actionable task with enough context to act on. Delete vague placeholders like "TODO: improve this" or "add more validation" because they express a feeling rather than a task.

What are the limitations of automated comment cleanup?▼

Judging whether a comment carries real information requires understanding intent, so borderline cases default to keeping the comment. The Skill also depends on the companion antislop core rules and does not restructure code that is genuinely hard to follow.