agentleFS
Sign inStart free
educlopezeduclopez/mallard/skills/no-comments/SKILL.md

no-comments

Skill4 starsChanged 13 days agoMITView on GitHub

Review the current diff for comments that apologize for the code (workarounds, "hack", "TODO fix later", "do not touch") and fix the cause instead of explaining it. Use when the user says "limpia comentarios", "no-comments", "quita los hacks comentados", "hay muchos comentarios raros", or after a change that left workaround comments behind.

68 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use poteto-help, setup-pstack 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.
  • ianclearySkill

    poteto-help

    Guides users through pstack setup, /poteto-mode, and picking the skill, playbook, or principle for a task. Type /poteto-help with a question.

    Also in 13 projects that use this

  • bnemaSkill

    setup-pstack

    Configure which Pi models pstack uses per role. Detects available provider/model specs and writes pstack's user configuration. Use for /setup-pstack, "configure pstack models", or changing pstack model choices.

    Also in 22 projects that use this

  • ianclearySkill

    principle-explain-the-number

    Apply before you trust, report, or act on a number you measured: a speedup, a regression, a throughput, a latency, or an eval result. Find what limits it, and rule out that it measured something other than the work you think.

    Also in 25 projects that use this

  • eryzerzSkill

    make-bot-ui

    Use when building a custom UI (page, dashboard, buttons) that should wake a Grok Bot over a webhook, when the user must provide a webhook sender key, or when exposing that UI on Tailscale.

    Also in 16 projects that use this

  • TheOnlyFusionCubeSkill

    maintain-formal-verification-skill

    Bring a project's formal verification back in line with the code after the code changes: find the commits that touched verified code, update the model, harness, or properties to describe the code as it is now, rerun, and say whether each failure is drift in the verification or a bug in the code. Use for /maintain-formal-verification-skill, \"is the model still true to the code\", or after merges and refactors that touched verified code without rechecking it.

    Also in 19 projects that use this

  • TheOnlyFusionCubeSkill

    create-formal-verification-skill

    Generate a project-local skill that formally verifies the code where a bug costs the most and tests reach the least, in any language, with whichever verification tool fits. Use for /create-formal-verification-skill, \"model-check this race\", \"prove this invariant\", or when concurrency, retries, state machines, parsers, or unsafe code need more than tests.

    Also in 21 projects that use this

  • +1 more from TheOnlyFusionCube

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 66 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:

    Describes what the code does: delete only if the code is already clear.

    line 25
  2. Distinctive:

    Lint or type suppression: check it is still needed; correctness and safety suppressions stay.

    line 28
  3. Distinctive:

    Never delete a comment you were not asked to touch in files outside the diff.

    line 31

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

no-comments

Adapted from pstack's no-comments. A comment that explains a workaround is a flag: the code surprised its author. Fix the surprise, then drop the comment. It does not strip useful comments, edit code outside the diff, or run a separate reviewer agent.

Scope

The caller's files or the diff against the base branch (main or master), including the working tree.

Steps

  1. List comments in scope and sort each:
    • Describes what the code does: delete only if the code is already clear.
    • Explains a workaround or a surprise: a flag. Find the root cause.
    • States a constraint ("do not remove", "talk to X first", vendor quirk, PrestaShop core behavior): keep, unless a type, test or lint can enforce it.
    • Lint or type suppression: check it is still needed; correctness and safety suppressions stay.
  2. For each flag, make the smallest root-cause fix in scope: delete the dead path, use the real API, drop the parameter. If the root cause is out of scope, make the smallest in-scope fix and report the rest as open.
  3. For each kept constraint, offer the cheapest in-scope enforcement (test, lint, check) and wait for the user's OK before adding it. If approved, encode, then delete the comment.
  4. Never delete a comment you were not asked to touch in files outside the diff. Never add a symptom guard.

Report

Comments deleted, flags fixed (file, one line), constraints kept with reason, enforcement offers, open items.

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.

Check your setup, free