agentleFS
DarthJonathanDarthJonathan/guac-skills/skills/no-comments/SKILL.md

no-comments

Skill0 starsChanged 18 days agoMITView on GitHub

Review comments for redundant narration and hidden design problems, preserving useful contracts and genuine constraints. Use for no-comments requests or focused cleanup.

68 other projects use a version of this.

Adopted by

Most recently taken up by

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

    Read the Codex runtime adapter once per session before using this skill.

    line 6
  2. Distinctive:

    When a permitted reviewer is useful, pass the comment reviewer prompt and exact scope to a native read-only subagent.

    line 12

“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

Read the Codex runtime adapter once per session before using this skill. Its tool, model, history, and authorization mappings apply to all linked instructions.

No comments

Review the scoped files or diff for comments that repeat code, conceal dead code, or document avoidable workarounds.

When a permitted reviewer is useful, pass the comment reviewer prompt and exact scope to a native read-only subagent. Otherwise perform the review directly. The parent owns any edits.

Preserve legal notices, public API contracts, non-obvious constraints imposed by external systems, useful issue references, and justified tooling directives. Inspect the surrounding implementation before judging a claim. A necessary suppression should not disappear merely because a reviewer dislikes comments.

For avoidable complexity, identify the specific symbol and a concrete structural improvement. Apply only changes within the user's scope and existing authorization. Verify that deleting or rewriting a comment did not change a generated artifact, tool behavior, or a required contract.

Report accepted changes, evidence-backed structural suggestions, and meaningful exceptions.

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.