deslop

Solid

Remove AI-generated code slop, unnecessary comments, and over-engineering from the current branch diff. Cleans up boilerplate, simplifies abstractions, strips defensive code, and in skill-file mode lints SKILL.md files for quality. Use when cleaning up code, simplifying, removing boilerplate, before committing, or when reviewing a skill before promoting it.

Code & Development 2,653 stars 257 forks Updated today

Install

View on GitHub

Quality Score: 83/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
0
Description 5%
100

Skill Content

# Remove AI Code Slop Check the diff against main and remove AI-generated slop introduced in the branch. ## Trigger Use after completing changes, before committing, or when code feels over-engineered. ## Commands ```bash git fetch origin main git diff origin/main...HEAD --stat git diff origin/main...HEAD ``` ## Workflow 1. Run diff commands to see all changes on the branch. 2. Identify slop patterns from the focus areas below. 3. Apply minimal, focused edits to remove slop. 4. Re-run `git diff origin/main...HEAD` to verify only slop was removed. 5. Run tests or type-check to confirm behaviour unchanged: `npm test -- --changed --passWithNoTests 2>&1 | tail -10` 6. Summarise what was cleaned. ## Focus Areas - Extra comments that state the obvious or are inconsistent with local style - Defensive try/catch blocks that are abnormal for trusted internal code paths - Casts to `any` used only to bypass type issues - Over-engineered abstractions for one-time operations (premature helpers, factories) - Deeply nested code that should be simplified with early returns - Backwards-compatibility hacks (renamed `_vars`, re-exports, `// removed` comments) - Features, refactoring, or "improvements" beyond what was requested - Added docstrings, type annotations, or comments on code that wasn't changed - Error handling for scenarios that can't happen in trusted internal paths ## Guardrails - Keep behavior unchanged unless fixing a clear bug. - Prefer minimal, focused edits over broad ...

Details

Author
rohitg00
Repository
rohitg00/pro-workflow
Created
5 months ago
Last Updated
today
Language
JavaScript
License
None

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

remove-ai-slops

Remove AI-generated code smells (slop) from branch changes or an explicit file list. Locks behavior with regression tests FIRST, then runs categorized cleanup via parallel `deep` agents in batches of 5, then verifies with quality gates. Covers 10 slop categories including performance equivalences, excessive complexity (object annotations, if/elif variant chains), and oversized modules (250+ pure LOC with mandatory modular refactoring). MUST USE when the user asks to "remove slop", "clean AI code", "deslop", "clean up AI-generated code", "remove AI slop", or wants to clean up AI-generated patterns from recent changes. Triggers - "remove ai slops", "clean ai code", "deslop", "cleanup AI generated", "remove AI slop", "clean up AI-generated code", "strip slop", "ai-slop cleanup".

66,701 Updated today
code-yeongyu
AI & Automation Listed

remove-ai-slops

Strip AI-generated code slop from changed files: double-guards, dead fallbacks, redundant re-validation, narrating comments, speculative flexibility, premature abstraction, and more. Each category pairs with a KEEP rule and a trust-boundary proof requirement, so cleanup never strips load-bearing validation or error handling. Triggers: 'remove ai slop', 'clean up generated code', 'de-slop', 'remove defensive clutter', 'strip ai slop', 'clean up ai-generated code'.

1 Updated 2 days ago
UtsavBalar1231
AI & Automation Featured

ai-slop-cleaner

Clean AI-generated code slop with a regression-safe, deletion-first workflow and optional reviewer-only mode

38,126 Updated today
Yeachan-Heo