Mmcp.market

deslop skill

by rohitg00·rohitg00/pro-workflow·2.9k stars

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.

A100/100content scan

Is the deslop skill safe?

Clean: nothing in its files matched our rules. We read 1 file in the folder on 2026-09-28.

No findings.

Install the deslop skill

A skill is a folder. Copy it into your agent's skills folder and the agent loads it when the task matches its description. 

git clone --depth 1 https://github.com/rohitg00/pro-workflow.git /tmp/pro-workflow
mkdir -p ~/.claude/skills
cp -r /tmp/pro-workflow/skills/deslop ~/.claude/skills/deslop
available in every project

In the Claude apps, zip the folder and upload it from the Skills settings. The folder on GitHub

The instructions your agent would load

SKILL.md as published, without the frontmatter. Read it on GitHub

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

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 rewrites.
  • Three similar lines of code is better than a premature abstraction.
  • If you remove something, verify it's truly unused first.
  • Keep the final summary concise (1-3 sentences).

Skill-file mode

When the target is a SKILL.md (not a code diff), lint it against the same slop instinct applied to prose. Run this before promoting a skill. Flag:

longer matches what it does. Cut it.

  • Stale lines - guidance written for an old version of the skill that no

linked reference. Push it down: in-skill step, then in-skill reference, then an external file behind a pointer.

  • Bloat - the skill runs past one screen with detail that belongs in a

Keep one source of truth.

  • Dead sentences - a line that changes nothing if deleted. Delete it.
  • Duplication - the same instruction stated in two places, so edits drift.

but never records the answer, cleans but never verifies).

  • Premature stop - the method ends before the work does (asks the question

can name in one word triggers and executes in fewer tokens.

  • Weak anchor - no single concept the skill turns on. A skill the reader

See rules/skill-conventions.mdc.

  • Missing invocation intent - no declared human-run vs auto-triggered mode.

adds, updates, or appends, or that duplicates its output on a second run.

  • Wrong write op - a state-changing skill that does not say whether it

Skill-file mode output: the flagged issues by line, the edits applied, the cleanup summary, and whether the skill is ready to promote.

Output (code mode)

  • List of slop patterns found with file locations
  • Edits applied
  • One-line summary of what was cleaned

More skills from rohitg00/pro-workflow

  • Aagent-teamsCoordinate multiple Claude Code sessions as a team — lead + teammates with shared task lists, mailbox messaging, and file-lock claiming. Patterns for team sizing, task decomposition, and when to use teams vs sub-agents vs worktrees.
  • Aauto-setupAuto-configure quality gates, hooks, and settings for a new project. Detects project type and sets up appropriate tooling. Use when onboarding a new codebase.
  • Abatch-orchestrationDecompose large-scale changes into independent units and spawn parallel agents in isolated worktrees. Use for migrations, refactors, codemods, and any change touching 10+ files with the same pattern.
  • Cbug-captureCapture a user-reported defect as a durable GitHub issue written in the project's own domain language. Explores the codebase in parallel for context but never leaks file paths or line numbers into the issue. Use when the user reports a bug conversationally, runs a QA pass, or says "file an issue", "log this as a bug", "capture this".
  • Acompact-guardSmart context compaction with state preservation. Saves critical files, task progress, and working state before compaction, restores after. Use before manual compact or when auto-compact triggers.
  • Acontext-engineeringMaster the four operations of context engineering — Write, Select, Compress, Isolate. Manage token budgets, compaction strategies, and context partitioning to keep AI sessions sharp and efficient.
  • Acontext-optimizerOptimize token usage and context management. Use when sessions feel slow, context is degraded, or you're running out of budget.
  • Acost-trackerTrack session costs, set budget alerts, and optimize token spend. Use to check costs mid-session or set spending limits.
  • Adesign-engineeringApply interface craft when building or reviewing UI - motion, easing, timing, springs, component feel, and visual foundations. Use when building a component, animation, transition, hover or press state, modal, drawer, toast, or when polishing an interface so it feels right. Says "make this feel better", "add an animation", "polish the UI", "review this component".
  • Adomain-modelingBuild the project's shared language and bounded contexts before writing code, so names stay consistent and the agent stops paraphrasing domain concepts. Produces a CONTEXT.md glossary and decision records. Use at the start of a project or feature, or when the codebase and the people describing it speak different languages.
  • Afile-watcherConfigure file watching hooks to auto-react to config changes, env file updates, and dependency modifications. Use to set up reactive workflows.
  • Aimprove-architectureAudit an area of the codebase and propose the smallest structural moves that improve it - untangle boundaries, kill duplication, fix seams, break cycles. Produces a prioritized plan and decision records, not a rewrite. Use when a codebase feels tangled, hard to change, or is becoming a ball of mud, or when asked to improve or refactor architecture.

All agent skills → · MCP servers