s-hiraoku/claude-harnesses · Archived

deslop

Remove AI-generated boilerplate (vague comments, unused try/except, defensive validation, restated docstrings) from changed code without changing behavior.

First seen Jun 13, 2026

Installation

$ npx skills add s-hiraoku/claude-harnesses --skill deslop

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from s-hiraoku/claude-harnesses · top by installs.

npx skills add s-hiraoku/claude-harnesses

Browse all from s-hiraoku/claude-harnesses

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

License LICENSE
Default branch main
Open issues 1
Status Archived

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents claude-code

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,451 B
  • docs SUMMARY.md 169 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 2 installs

SKILL.md

Deslop

Use this workflow when changes on the current branch contain visibly LLM-generated patterns that hurt readability or maintainability.

Common slop signatures

  • Comments that restate the next line verbatim.
  • try/except Exception that re-raises with a wrapper message and no other handling.
  • Input validation for cases the type system already rules out.
  • "Helper" functions used exactly once.
  • Multi-paragraph docstrings on private functions.
  • "Added for issue #N" / "Used by foo" comments that bind code to the conversation.
  • Unreachable defensive branches (if config is not None after a non-Optional construction).

Workflow

  1. List changed files: git diff origin/main...HEAD --name-only.
  2. For each non-trivial file, read the diff and look for the signatures above.
  3. Apply minimal removals. Preserve every observable behavior.
  4. Re-run targeted tests for each touched module.

Constraints

  • Do not delete genuine error handling at system boundaries (HTTP, subprocess, file IO).
  • Do not delete comments that explain a non-obvious WHY.
  • If unsure, leave it and propose the removal in the report.

Final Report

  • files changed
  • slop categories removed (one line each)
  • tests run and result
  • proposals not applied