deslop

Detect and remove AI-generated artifacts from codebases with structured JSON output.

951|110|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/agent-sh/agentsys --skill deslop-agent-sh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deslop
Source: https://github.com/agent-sh/agentsys/tree/main/.kiro/skills/deslop
Command: npx skills add https://github.com/agent-sh/agentsys --skill deslop-agent-sh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clean AI slop from codebases by identifying and removing non-functional or distracting artifacts, such as stray debug statements and ghost code, to improve readability and maintainability.

Core Features & Use Cases

  • Detects and highlights debug statements, placeholder text, and dead code.
  • Recommends or applies automated cleanups in CI or local workflows.
  • Use Case: A development team wants to remove all temporary logs before release to reduce noise and risk.

Quick Start

Run the deslop skill to scan your repository for AI slop and optionally auto-fix issues.

Frequently Asked Questions about deslop

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

FAQPage Schema
How do I remove AI generated slop and debug statements from my codebase?

To remove AI generated slop from a codebase, you can run a full-project scan or diff-based scope to identify stray debug statements, placeholder text, and dead code, then apply automated fixes or generate a structured report for review.

What is the best way to detect dead code and placeholder text before a release?

Detecting dead code and placeholder text before release is best handled by a deterministic, multi-phase static analysis pipeline that highlights non-functional artifacts and optionally integrates directly into CI workflows to reduce noise and risk.

Does static analysis for code cleanup work across multiple programming languages?

Static analysis for code cleanup applies to software repositories across multiple programming languages, using a deterministic pipeline that relies on an external detection script and optional repository-map analysis to identify artifacts.

How do I integrate dead code detection into my CI pipeline?

Integrating dead code detection into a CI pipeline is done by running the analysis to produce a structured JSON output, which is suitable for consumption by automated fixers and continuous integration systems to enforce repository hygiene.

What is the difference between a full-project scan and a diff-based scope for code cleanup?

A full-project scan examines the entire repository for AI slop and distracting artifacts, while a diff-based scope limits the static analysis to recent changes, allowing developers to target code cleanup precisely within their active workflows.

When should I avoid using automated fixes for repo hygiene?

Automated fixes for repo hygiene should be avoided when you need strict manual oversight, though the pipeline can alternatively return structured reports highlighting debug statements and ghost code without directly modifying the source files.