ai-slop-cleaner
Run an anti-slop cleanup/refactor/deslop workflow
Skill by Yeachan-Heo
Chalk Labs
Need help deploying ai-slop-cleaner?
Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.
Install
Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.
npx agentmarket install skill/yeachan-heo-ai-slop-cleaner-4f41cb
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Use cases: productivity
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions: not checked yet.
What's inside
- Skill name
ai-slop-cleaner- Description
- Run an anti-slop cleanup/refactor/deslop workflow
- License
- MIT
- Instructions
- 69 lines in SKILL.md · view on GitHub
Agent Skills spec issues
- files: referenced but missing: templates/AGENTS.md
Files (1)
- SKILL.md
SKILL.md (first lines)
# AI Slop Cleaner Task Card Use this bounded helper for cleanup/refactor/deslop work, not as a competing top-level workflow. Shared operating invariants live in `templates/AGENTS.md`; this card defines scope, smell taxonomy, passes, and evidence. ## When to use and inputs Use when working code is bloated, noisy, repetitive, over-abstracted, or AI-generated; the user requests cleanup/refactor/deslop; or a follow-up left duplicate/dead code, weak boundaries, missing tests, fallback-like paths, or wrappers. Inputs are the requested feature/files and behavior to preserve. A file list scope is valid; keep the pass bounded to it. Limit the pass to the calling task's changed files unless broader cleanup was requested. ## Before editing 1. **Lock behavior with regression tests first**: identify behavior to preserve, run/add the narrowest targeted tests, and cover both primary and preserved compatibility/fail-safe fallback paths. 2. **Create a cleanup plan before code**: list scope and smells, include fallback findings/classifications/escalation, and order safest/highest-signal fixes first. 3. **Inventory fallback-like code** in scope: quick hacks, temporary workaround, temporary fallback, just bypass, just skip, fallback if it fails, swallowed errors, silent defaults, broad compatibility shims, and duplicate alternate execution paths. 4. Classify each fallback: **Masking fallback slop** hides evidence, bypasses the contract, suppresses validation, swallows failures, silently defaults, or adds untested paths; **Grounded compatibility/fail-safe fallback** is narrow at an external/version/fail-safe boundary, documents rationale, preserves failure evidence, and tests primary plus fallback. 5. Prefer root-cause repair, deletion, boundary repair, or explicit failure behavior. For broad/ambiguous/cross-layer/architectural findings, invoke `$ralplan` for consensus resolution; when already inside ralplan, ultragoal, team, or another OMX workflow, do not spawn a nested `$ralplan`—attach the finding to the active handoff. ## Smell taxonomy and passes Classify before changing: - **Fallback-like code**: masking fallbacks, workaround branches, bypasses, swallowed errors, silent defaults, broad shims, alternate paths. - **Duplication**: repeated logic, copy-paste branches, redundant helpers. - **Dead code**: unused/unreachable code, stale flags, debug leftovers. - **Needless abstraction**: pass-through wrappers, speculative indirection, single-use layers. - **Boundary violations**: hidden coupling, leaky responsibilities, wrong-layer imports/side effects. - **Missing tests**: behavior not locked or edge cases uncovered. - **UI/design slop**: context-sensitive signals, not absolute bans; preserve intentional brand, design-system, accessibility, or product-context exceptions. Challenge Korean body text at 11-12px (generally 14px or larger); gratuitous box shadows; repetitive eyebrow + title + description + paragraph stacks and generic emoji badges; default AI blue/purple such as `#3B82F6`; reflexive 3-column or 4-column grids; and extreme gradients unless justified by context. Resolve the fallback-like code resolution gate first, then one smell at a time: **Pass 1: Dead code deletion**; **Pass 2: Duplicate removal**; **Pass 3: Naming/error handling cleanup**; **Pass 4: Test reinforcement**. Re-run targeted verification after each pass and avoid unrelated refactors. Prefer deletion/existing utilities; no new abstractions or dependencies unless explicitly required. ## Evidence/output contract Report: ```text AI SLOP CLEANUP REPORT Scope: [files/feature] Behavior Lock: [targeted tests added/run] Cleanup Plan: [bounded smells/order] Fallback Findings: [finding -> masking fallback slop | grounded compatibility/fail-safe fallback -> escalation] UI/Design Findings: [none/N/A or signal -> action/defer -> intentional rationale] Passes Completed: [resolution gate; Passes 1-4] Quality Gates: Regression tests, Lint, Typecheck, Tests, Static/security scan (PASS/FAIL/N/A) Changed Files: [path -> simplification] Remaining Risks: [none or deferred item] ``` Include changed files, simplifications, fallback classifications/escalation status, tests/diagnostics/build checks run, UI findings when relevant, and deferred risks. Keep writer/reviewer separation for cleanup plans and approvals. ## Exit condition Stop when the requested scope has behavior-lock evidence, each selected smell pass is complete or explicitly deferred with rationale, verification is reported, and no unrelated files or temporary artifacts remain. Never present an unverified cleanup as complete; escalate a real architectural blocker rather than masking it.
From Yeachan-Heo/oh-my-codex, MIT.
Signals
- Stars
- 33,621
- Forks
- 2,549
- Open issues
- 1
- Last commit (this folder)
- Sep 9, 2026 (2 months ago)
- Last release
- Oct 24, 2026 (25 days ago)
From GitHub (fetched Oct 24, 2026).
Details
- License
- MIT
- Repository
- github.com/Yeachan-Heo/oh-my-codex
- Website
- oh-my-codex.dev
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
- Source
- GitHubgithub-graphql
Done for you
Rather not set it up yourself?
Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.
See how we build AI agents →Read the case studies
Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.
- launches shipped
- 50+
- launches shipped
- media placements
- 500+
- media placements
- founders on every account
- 2
- founders on every account
Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block
Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.
Get ai-slop-cleaner running in your business
Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.
Cite this page
ai-slop-cleaner skill. Agent Mart. https://agentmart.dev/skills/yeachan-heo-ai-slop-cleaner-4f41cb (last updated 2026-10-24)