← ClaudeAtlas

desloplisted

Scan the codebase for AI-generated slop in comments and docstrings — temporal markers, self-referential AI framing, narrative WHAT-comments, marketing padding — and propose tightened rewrites. Use when the user wants to audit pending changes or the whole codebase for verbose, low-value commentary left by other assistants (Copilot, Gemini, GPT, etc.).
ajbarea/techne · ★ 0 · AI & Automation · score 75
Install: claude install-skill ajbarea/techne
# Deslop Find and remove low-value, AI-generated commentary in source files. Keep comments that explain a non-obvious *why*; trim or delete everything else. ## Repo context ```! cat .claude/skill-context.md 2>/dev/null || echo "(no .claude/skill-context.md — skill will use generic defaults for skip paths and scan split)" ``` The injected `## scan_scope` section (if present) supplies this repo's skip-path list and subagent scan-area split. The `## slop_ground_truth` section (if present) names the repo's source of truth for performance/scale claims — used when filtering unmeasured numeric claims. Use those over the generic defaults below when available. ## What counts as slop **Cut:** - **Temporal markers** — "(April 2026 best-practice order)", "as of 2024", "latest version". These rot. - **Self-referential AI framing** — "designed so an AI assistant who did not see the live terminal can reconstruct", "AI-DEBUG HINTS", "helps LLMs understand", "for model consumption". - **Narrative WHAT-comments** — `# Now we iterate through the list`, `# Return the result`. If the identifier already tells you, the comment is dead weight. - **Marketing language** — "robust", "comprehensive", "elegant", "best-practice", "production-ready", "seamless", "powerful", "effortlessly", "with ease", "painlessly", "simply", "just" (as filler), "out of the box", "blazingly", "lightning-fast", "battle-tested", "state-of-the-art", "cutting-edge" when describing your own code. See `${CLAUDE_PLUGIN_ROO