id-slop

Scan codebases for AI-generated slop and compile a prioritized removal plan.

1|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/Trecek/useful-claude-skills --skill id-slop-trecek
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: id-slop
Source: https://github.com/Trecek/useful-claude-skills/tree/main/.claude/skills/id-slop
Command: npx skills add https://github.com/Trecek/useful-claude-skills --skill id-slop-trecek

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify AI-generated slop in the codebase—useless comments, backward compatibility hacks, deprecation notices, dead code, and other technical debt left by AI assistants. Use when you want to clean up AI-generated drift in your repository.

Core Features & Use Cases

  • Detects Phase Reference Comments, Backward Compatibility Hacks, Deprecation Notices, and Dead Code with clear categorization and line-level context.
  • Generates a structured removal plan in temp/id-slop/ and validates it with a dry walkthrough prior to any modification.
  • Produces a prioritized report with file paths, line numbers, and slop types to guide engineers in safe cleanup.

Quick Start

Identify slop by saying "id slop" to initiate the scan and review the generated plan at temp/id-slop/slop_removal_plan_YYYY-MM-DD_HHMMSS.md before applying any changes.

Frequently Asked Questions about id-slop

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

FAQPage Schema
How do I find and remove AI-generated slop in my codebase?

This Skill scans large repositories to identify AI-generated slop—useless comments, backward compatibility hacks, deprecation notices, and dead code—then compiles a prioritized removal plan with file paths, line numbers, and slop categories.

What is AI-generated slop and how does it affect technical debt?

AI-generated slop is technical debt left by AI assistants, including useless comments, backward compatibility hacks, deprecation notices, and dead code. It accumulates as drift in a repository and requires structured detection and prioritized cleanup.

How do I generate a dead code and useless comment removal plan?

You generate a removal plan by scanning the codebase for dead code and useless comments, which produces a structured markdown file with prioritized file paths and line numbers to guide safe code cleanup.

Can I validate a slop removal plan before applying changes to the repository?

Yes, you can validate the slop removal plan before applying changes by using the dry walkthrough feature to review file paths and line numbers safely prior to any modification.

Does this dead code cleanup tool work across different programming languages?

Yes, the dead code and slop cleanup tool applies to large repositories across multiple languages, scanning for technical debt categories like deprecation notices and backward compatibility hacks regardless of language.

What are the limitations of automated AI slop detection?

Automated AI slop detection generates a removal plan with file paths and line numbers, but engineers must review the dry walkthrough before applying changes to ensure safe cleanup of technical debt without breaking existing functionality.