antislop-code

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

1|Updated Aug 29, 2026
One-click install
npx skills add https://github.com/IzzatFirdaus/task-enterprise-api --skill antislop-code-izzatfirdaus
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: antislop-code
Source: https://github.com/IzzatFirdaus/task-enterprise-api/tree/main/.gemini/skills/antislop-code
Command: npx skills add https://github.com/IzzatFirdaus/task-enterprise-api --skill antislop-code-izzatfirdaus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI coding agents often leave behind generic, decorative, or redundant comments—banner separators, step-by-step narration, signature echoes—that add noise without information. This Skill gives agents concrete rules to clean up those comments while protecting the ones that carry real meaning. ## Core Features & Use Cases - Slop Comment Detection: Identifies decorative separators, restated obvious lines, workflow narration, empty labels, vague TODOs, signature echoes, decorative emoji, and end markers, each with a Tell/Why/Fix pattern. - 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 module full of // Step 1: Validate input and // ======= HELPERS ======= comments, run this Skill to strip the noise and keep only the comments that explain non-obvious behavior. ## Quick Start Review the comments in this file and remove any generic AI-style comments while keeping the ones that explain real business logic or constraints.

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?▼

Identify comments that restate the obvious, narrate workflow steps, or serve as decorative separators, then remove them while keeping comments that explain business logic, security, or edge cases. This Skill provides Tell/Why/Fix patterns for each slop category.

What kinds of code comments should be deleted after AI code generation?▼

Delete decorative banner separators, step-by-step narration, empty labels like "Main logic", vague TODOs, signature-echoing docblocks, decorative emoji, and end-of-block markers. These add reading load without adding information.

Which code comments should never be removed during cleanup?▼

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

Does cleaning up comments risk changing the code behavior?▼

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

When should a TODO comment be kept versus removed?▼

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