antislop-code

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

Updated Aug 1, 2026
One-click install
npx skills add https://github.com/dxiiren/project-skeleton --skill antislop-code-dxiiren
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: antislop-code
Source: https://github.com/dxiiren/project-skeleton/tree/main/.claude/skills-optional/anti-slop/antislop-code
Command: npx skills add https://github.com/dxiiren/project-skeleton --skill antislop-code-dxiiren

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI coding agents tend to fill codebases with decorative, redundant, or noisy comments — banner separators, step-by-step narration, signature echoes, and vague TODOs — that add reading load without adding information. This Skill gives agents concrete rules to strip that slop while protecting comments that carry real knowledge. ## Core Features & Use Cases - Slop Pattern Detection: Identifies eight comment anti-patterns including decorative separators, restating the obvious, workflow narration, empty labels, vague placeholders, signature echoes, decorative emoji, and end markers. - Preservation Guardrails: Explicitly protects comments explaining business logic, security, performance trade-offs, API contracts, workarounds, and edge cases. - Scope Safety: Enforces a strict guardrail that only comments may be modified — never executable code, identifiers, formatting, or logic. - Use Case: After an AI agent generates a large feature, run this Skill to clean the diff so every remaining comment explains something the code does not already show. ## Quick Start Review the comments in the files I just changed, remove any generic AI-slop comments, and keep only the ones that explain non-obvious behavior.

Frequently Asked Questions about antislop-code

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

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

Apply the anti-slop comment rules: delete decorative separators, restatements of the obvious, 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 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. A comment earns its place when it states a reason, constraint, or non-obvious behavior.

Does cleaning code comments risk changing program behavior?

No. The Skill enforces a strict scope guardrail: only comments may be modified. Executable code, identifiers, imports, formatting, indentation, whitespace, control flow, and logic are never touched, so runtime behavior stays identical.

When should a TODO comment be removed versus kept?

Remove vague TODOs like "Improve this" or "Add more validation" because they name a feeling rather than a task. Keep a TODO only when it names a specific, actionable task with enough context for someone to act on it.

What are the limitations of automated comment cleanup?

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