smithery.ai

deslop-code

Clean up AI-generated code changes by reviewing diffs against main and removing stylistic or structural artifacts (over-commenting, unnecessary defensive checks, try/catch noise, any-casts, inconsistent style).

First seen Apr 13, 2026

Installation

$ npx skills add https://smithery.ai

Summary

  • Clean up AI-generated code changes by reviewing diffs against main and removing stylistic or structural artifacts (over-commenting, unnecessary defensive checks, try/catch noise, any-casts, inconsistent style).
  • Use when asked to “remove AI code slop,” “humanize” changes, or align a branch’s edits with existing codebase conventions.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,414 B
  • docs SUMMARY.md 362 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

Deslop Code

Overview

Strip AI-generated artifacts from a branch by comparing against main and aligning edits with local conventions and surrounding code style.

Workflow

  1. Establish baseline
  • Use git diff against main to identify AI-introduced changes.
  • Review surrounding context in each file to understand local conventions.
  1. Remove slop patterns
  • Delete comments that read like explanations, narrations, or redundant restatements of code.
  • Remove defensive checks or try/catch blocks that are inconsistent with trusted code paths or nearby style.
  • Replace any-casts or similar type escapes with proper typing or remove them if unnecessary.
  • Normalize style to match the file (naming, ordering, error handling, control flow).
  1. Verify consistency
  • Ensure behavior remains unchanged unless removal requires a small refactor to restore intended behavior.
  • Keep changes minimal and localized; avoid refactors not needed for cleanup.
  1. Report
  • End response with a 1–3 sentence summary of what changed.