agentleFS
iyazerskiiyazerski/dev-flows-plugin/skills/deslop/SKILL.md

deslop

Skill0 starsChanged 4 months agoMITView on GitHub

Radically reduce comments, low-value tests, speculative defensive code, and borrow-checker workarounds. Use when the user asks to de-slop code or cut boilerplate.

130 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use simple-issue-description, control-cli and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • JwuthriSkill

    simple-issue-description

    Turn a rough bug report, feature request, support note, or pull request into a short, plain-language issue focused on the problem and desired behavior. Use when a contributor asks to simplify an issue, explain what a PR is for, create the corresponding issue for a PR, remove implementation detail from a report, or invokes /simple-issue-description.

    Also in 4 projects that use this

  • ElyzeSolutionsSkill

    control-cli

    Build or adapt a local harness to drive, inspect, and profile an interactive CLI or TUI without external services. Use for CLI UX checks, startup regressions, memory leaks, hangs, prompt flows, or terminal demos.

    Also in 6 projects that use this

  • JwuthriSkill

    openseo-review-web-content

    Write and review content for the OpenSEO website (web/) — blog posts, guides, feature pages, FAQs. Distills the philosophy for on-brand, useful, accurate content. Use whenever adding or editing user-facing prose in web/content or web/src.

    Also in 4 projects that use this

  • learnerLjSkill

    verify-this

    Verify a claim with fresh local evidence: restate it falsifiably, capture baseline and treatment, compare artifacts, and return VERIFIED, NOT VERIFIED, or INCONCLUSIVE.

    Also in 6 projects that use this

  • ElyzeSolutionsSkill

    control-ui

    Build or adapt a local browser/CDP harness to drive and inspect a web, IDE, or Electron UI. Use for local UI verification, screenshots, accessibility snapshots, perf profiles, visual diffs, or reproducing UI bugs.

    Also in 7 projects that use this

  • ten9876Skill

    papercuts

    Read-only AetherSDR issue triage that surfaces the UX papercuts, bugs, and regressions you can fix AND prove today with the agent automation bridge. Use when the user says $papercuts or /papercuts, or asks to "find papercuts", "what can I fix and prove today", "triage bridge-provable issues", "what UX bugs can the bridge close", "sort issues by priority I can knock out", or otherwise wants a curated, lifecycle-aware (design→code→prove) shortlist of issues — NOT the label-and-respond /triage workflow. This is the discovery step that feeds /fb. Strictly read-only: it never labels, comments, closes, or edits issues.

    Also in 4 projects that use this

  • +5 more from Jwuthri

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 128 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Comments: Keep only comments required by the language or tooling, legal notices, and short explanations of non-obvious behavior or …

    line 11
  2. Distinctive:

    Remove: Create a branch from the updated default branch.

    line 17

“Common” is measured: kept by at least 6 in 10 of the 128 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Deslop

Make the cleanup directly within the requested scope. Aim for a radical reduction in unnecessary code, not cosmetic edits or a deletion quota. This is not a general hardening or refactoring pass.

  1. Review:

    • Comments. Keep only comments required by the language or tooling, legal notices, and short explanations of non-obvious behavior or constraints. Delete narration, repeated signatures, obvious documentation, and stale notes.
    • Tests. Keep a small set of meaningful tests for production behavior and real regressions. Delete redundant, trivial, implementation-detail, and coverage-only tests. Remove tests for non-production features and paths, including internal-only scripts and utilities. Judge this by what the code does, not its directory: a production data migration is a production path. Merge similar tests when they share setup and behavior. Remove orphaned fixtures and test-only dependencies. Don't add replacement tests just to retain coverage.
    • Defensive code. Delete impossible checks, speculative safeguards, silent fallbacks, obsolete compatibility paths, and costly handling for extremely rare cases. Verify assumptions against actual callers, types, schemas, data, and decision history. Don't keep speculative handling just because it exists. Keep protections for real security, I/O, concurrency, and data-integrity risks. Fail clearly for unsupported cases rather than pretending success.
    • Borrow-checker workarounds. In Rust, remove unnecessary clones, intermediate collections, dummy state, and indirection introduced only to work around borrowing. Prefer moves, shorter borrows, disjoint fields, and behavior on the owning type. Leverage ownership and the compiler's guarantees. Don't remove copies needed by actual callers or replace safe code with unsafe, unchecked operations, or runtime borrow checks just to shorten it.

    Review the full requested scope across all four areas, not just obvious lint fixes.

  2. Remove. Create a branch from the updated default branch. Apply verified cuts in small, coherent edits. Prefer deletion and existing helpers over replacement scaffolding or new abstractions. Remove one chunk at a time, and $commit each chunk.
  3. PR. $draft-pr and mark it ready. When CI passes, merge it.
  4. Release. Find out how this repo releases: recent release commits and tags, a changelog, release scripts, or CI workflows. Follow the same process for the merged changes, for example bumping the version or pushing a tag. If merging to the default branch already is the release, do nothing.
  5. Wrap up. Summarize what was removed, which meaningful tests and protections remain, checks run, and rare cases deliberately left unsupported.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.