mcpField
T
technical-deslop

technical-deslop

github.com/vincentkocDevelopment11190 installsUpdated 2d ago
Repository

About technical-deslop

technical-deslop is a repository-aware skill for cleaning staged or branch diffs while preserving behavior. It helps developers remove unnecessary code and align touched files with local conventions before review.

Key features

  1. 01Focuses cleanup on changed hunks
  2. 02Removes redundant comments and defensive branches
  3. 03Checks for idiomatic casts and style consistency
  4. 04Preserves behavior unless changes are requested
  5. 05Summarizes the cleanup performed

Use cases

  1. 01Preparing a diff for review or a pull request
  2. 02Normalizing code after automated generation
  3. 03Cleaning up over-explained or inconsistent changes

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/vincentkoc/dotskills --skill technical-deslop

After installing, type/technical-deslopin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

agents/
openai.yaml
references/
playbook.md
slop-patterns.md

Details

From the project README

Technical Deslop

Purpose

Clean branch/staged diffs by removing AI-style slop and restoring repo-consistent style without changing behavior.

When to use

  • A diff feels over-explained, overly defensive, or inconsistent with surrounding code.
  • You need a final cleanup pass before review/PR.
  • You want to normalize style after automated generation.

Workflow

  1. Capture scope with git diff --cached and git diff $(git merge-base origin/main HEAD)..HEAD.
  2. Focus only on changed hunks (or user-scoped files).
  3. Apply the cleanup sequence in references/playbook.md.
  4. Remove slop patterns: redundant comments, unnecessary defensive branches, non-idiomatic casts, and style drift.
  5. Re-check behavior boundaries: no logic changes unless the user explicitly requested them.
  6. Report a short 1-3 sentence summary of cleanup performed.

Read references/slop-patterns.md for detection rules and references/playbook.md for execution order.

Inputs

  • Optional file scope (FILES) or explicit user file targets.
  • Current branch diff and staged diff.
  • Repository conventions from local instructions/config.

Outputs

  • Behavior-preserving cleanup in touched files.
  • Minimal summary of what was normalized and where.

Comments

Markdown supported