de-slop

Detect and fix AI-generated code anti-patterns across Rust, Python, TypeScript, Go, and Shell.

2|Updated Sep 12, 2016
One-click install
npx skills add https://github.com/paulnsorensen/dotfiles --skill de-slop-paulnsorensen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: de-slop
Source: https://github.com/paulnsorensen/dotfiles/tree/main/claude/skills/de-slop
Command: npx skills add https://github.com/paulnsorensen/dotfiles --skill de-slop-paulnsorensen

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Detects and fixes AI-generated code anti-patterns across Rust, Python, TypeScript, Go, and Shell, producing idiomatic, maintainable code.

Core Features & Use Cases

  • Cross-language pattern detection to identify common anti-patterns such as verbose comments, defensive error handling, and unnecessary abstractions.
  • Language-specific fixes that rewrite code to idiomatic constructs and explain the rationale for each change.
  • Use cases include post-generation cleanup, code review hygiene, and pre-commit checks to ensure high quality before merging.

Quick Start

Provide the AI-generated code and request de-slop cleanup across the detected languages.

Frequently Asked Questions about de-slop

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

FAQPage Schema
How do I fix AI-generated code anti-patterns in Python and Rust?

To fix AI-generated code anti-patterns, you run a cleanup process that detects verbose comments and unnecessary abstractions, rewriting your Python and Rust code into idiomatic, maintainable constructs while explaining the rationale for each change.

What are common AI-generated code anti-patterns to look for during code review?

Common AI-generated code anti-patterns include verbose comments, defensive error handling, and unnecessary abstractions. Detecting these patterns during code review ensures cross-language code hygiene and maintainability before merging changes.

Can I use automated code cleanup for pre-commit checks across multiple languages?

Yes, you can use automated code cleanup as a pre-commit check across multiple languages. It detects and rewrites problematic AI-generated patterns in Rust, Python, TypeScript, Go, and Shell to ensure clean outputs before merging.

Does this code cleanup approach work with TypeScript, Go, and Shell scripts?

Yes, this code cleanup approach works with TypeScript, Go, and Shell scripts. It reads language-specific references to detect anti-patterns and applies idiomatic fixes across all five supported languages.

What is the best way to make AI-generated code more idiomatic and maintainable?

The best way to make AI-generated code idiomatic is to apply a targeted cleanup that rewrites problematic patterns into language-specific constructs. This process reads language references and explains the rationale for each change to ensure long-term maintainability.