antislop-code

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

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

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 instead of information. This Skill gives agents concrete rules to strip that slop while protecting comments that carry real meaning, and it never modifies the code itself. ## Core Features & Use Cases - Slop Pattern Detection: Identifies decorative separators, obvious restatements, workflow narration, empty labels, vague TODOs, signature echoes, decorative emoji, and end markers, each with a Tell / Why / Fix structure. - Preservation Rules: Explicitly protects comments explaining business logic, security, performance trade-offs, concurrency, API contracts, workarounds, and edge cases. - Scope Guardrail: Restricts edits strictly to comments — executable code, identifiers, imports, formatting, and logic are never touched. - 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 Review the comments in this file, remove the ones that restate the obvious or decorate sections, and keep only comments that explain why the code behaves 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 useless AI-generated comments from code?▼

Identify comments that restate the obvious, narrate steps, or decorate sections, then delete them while keeping comments that explain why the code behaves a certain way. This Skill provides a checklist of slop patterns with fixes for each.

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

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

Does cleaning up comments risk changing the code behavior?▼

No. This Skill enforces a strict scope guardrail: only comments are modified. Executable code, identifiers, imports, formatting, indentation, whitespace, control flow, and logic are never touched.

Are TODO comments always considered noise?▼

Only vague TODOs like "improve this" or "add more validation" are treated as slop because they name a feeling instead of a task. A TODO that names a specific, actionable task with enough context to act on should be kept.

When should I not remove a comment that looks redundant?▼

Do not remove documentation that explains business rules, edge cases, assumptions, algorithms, limitations, side effects, or security implications, even if it sits near an obvious signature. When in doubt, leave the comment in place.