Agent Skills › evolution-foundation/evo-nexus › dev-ai-slop-cleaner

dev-ai-slop-cleaner

GitHub

用于清理AI生成代码中的冗余内容，如单用辅助函数、过度抽象、泛化命名和不必要的配置。在代码生成后触发，提升代码简洁性与可读性。

.claude/skills/dev-ai-slop-cleaner/SKILL.md evolution-foundation/evo-nexus

Trigger Scenarios

用户指令清理AI生成的代码完成功能开发或批量文件变更后的代码审查

Install

npx skills add evolution-foundation/evo-nexus --skill dev-ai-slop-cleaner -g -y

More Options

Non-standard path

npx skills add https://github.com/evolution-foundation/evo-nexus/tree/main/.claude/skills/dev-ai-slop-cleaner -g -y

Use without installing

npx skills use evolution-foundation/evo-nexus@dev-ai-slop-cleaner

指定 Agent (Claude Code)

npx skills add evolution-foundation/evo-nexus --skill dev-ai-slop-cleaner -a claude-code -g -y

安装 repo 全部 skill

npx skills add evolution-foundation/evo-nexus --all -g -y

预览 repo 内 skill

npx skills add evolution-foundation/evo-nexus --list

SKILL.md

Frontmatter

{
    "name": "dev-ai-slop-cleaner",
    "description": "Post-AI-generation cleanup — remove single-use helpers, over-abstractions, generic naming, and unnecessary configurability. Use after dev-autopilot or any LLM-generated code burst."
}

Dev AI-Slop Cleaner

Derived from oh-my-claudecode (MIT, Yeachan Heo). Adapted for the EvoNexus Engineering Layer.

Cleanup pass for code generated by AI. Removes the typical bloat: single-use helpers, over-abstractions, generic names like processData(), unnecessary configurability that wasn't asked for.

Use When

After dev-autopilot finishes a feature
After @bolt-executor produces a multi-file change
Post-burst generation that wasn't carefully scoped
User says "deslop", "clean up the AI slop", "remove the bloat"

Do Not Use When

Hand-written code (no slop signature)
Code that's intentionally extensible (talk to @apex-architect first)

What to Look For

Signature 1: Single-use helpers

// SLOP
function calculateSum(a: number, b: number): number { return a + b; }
const total = calculateSum(price, tax);

// CLEANED
const total = price + tax;

Signature 2: Over-abstractions

// SLOP
class TimeoutConfigManager {
  private static instance: TimeoutConfigManager;
  static getInstance() { ... }
  setTimeout(ms: number) { ... }
  getTimeout() { ... }
}

// CLEANED
const TIMEOUT_MS = 5000;

Signature 3: Generic naming

// SLOP
function processData(data: any): any { ... }

// CLEANED
function parseCSVRow(row: string): User { ... }

Signature 4: Unrequested configurability

// SLOP
function fetchUser(id: string, options?: { retries?: number, backoff?: number, timeout?: number, cache?: boolean }) { ... }

// CLEANED (if retries/etc. weren't asked for)
function fetchUser(id: string) { ... }

Signature 5: TODO/HACK comments without context

Remove or convert to actual issues.

Workflow

Scan the recent diff for the 5 signatures above
For each match, propose the cleaned version
Hand off to @bolt-executor to apply (or @zen-simplifier for batch cleanup)
Run dev-verify to confirm behavior is unchanged
Save report to workspace/development/research/[C]slop-cleanup-{component}-{date}.md