agentleFS
openclawopenclaw/openclaw-enterprise/.agents/skills/deslop/SKILL.md

deslop

Skill454 starsChanged 10 days agoMITView on GitHub

Clean only the current Enterprise diff before autoreview, preserving behavior, security boundaries, required TODOs, and useful test-intent comments.

126 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

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

  • 0

    Common

    Most of the 125 edited versions we read keep these.

  • 3

    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:

    Keep cleanup confined to the current diff and strictly behavior-neutral.

    line 8
  2. Distinctive:

    Keep real fail-closed checks, authorization and credential boundaries, configuration rejection, and attributable audit behavior.

    line 42
  3. Distinctive:

    Use enterprise-testing for proportional verification of edits and run git diff --check.

    line 52

“Common” is measured: kept by at least 6 in 10 of the 125 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

Keep cleanup confined to the current diff and strictly behavior-neutral. Use it before requested autoreview; cleanup does not replace correctness or safety review.

For readability choices in the current diff, consult the relevant sections of Readable code on functions, values, composition, and state ownership. Apply those examples within this skill's behavior-neutral scope.

Scope and checklist

Establish the intended branch base from the PR or repository metadata. Inspect committed changes from its merge base to HEAD, plus staged, unstaged, and relevant untracked changes. Preserve unrelated work; never sweep the repository or change the base to make the cleanup larger. Read surrounding code to judge each hunk.

Look for:

  • Comments that narrate syntax or repeat code without explaining intent.
  • Unnecessary intermediate variables or one-use helpers that add no meaning.
  • Type assertions such as as any or as unknown as T that hide a type problem.
  • Defensive checks, catch blocks, retries, aliases, or fallbacks that appear inconsistent with the supported contract.
  • Naming, imports, formatting, or control flow inconsistent with nearby code and Enterprise style.

These patterns require judgment. Apply only trivial, demonstrably behavior-neutral edits. Removing a guard, catch, retry, fallback, or type cast can change behavior or expose a real type-contract defect: leave uncertain or functional changes in place and report them for separate review. Do not hide errors with wider types or replace security checks with assumptions.

Preserve required intent

Keep real fail-closed checks, authorization and credential boundaries, configuration rejection, and attributable audit behavior. Redundancy alone is not evidence that a security check is removable.

Preserve deferred-work TODOs while the capability remains unimplemented. Preserve integration-test comments that explain scenarios, non-obvious setup, expected outcomes, or security invariants; remove only narration that contributes no such information. Do not label permanent security boundaries as temporary work.

Use enterprise-testing for proportional verification of edits and run git diff --check. If behavior neutrality cannot be established, report the candidate instead of applying it as style work. Summarize in one to three sentences what changed and any non-trivial candidates left for the author.

Provenance

Adapted from OpenClaw; see source and intentional adaptations.

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.