agentleFS
StosanStosan/Claude-Skills-for-engineering-teams/skills/code-commenter/SKILL.md

code-commenter

Skill2 starsChanged 4 days agoNo licenceView on GitHub

Use this skill whenever the user wants to add comments, docstrings, or inline documentation to code. Trigger when the user says things like "add comments to this code", "document this function", "explain this code with comments", "add docstrings", "comment this", "make this code self-explanatory", "add inline comments", "document why this works the way it does", "help a new developer understand this", "annotate this code", or pastes code and asks for it to be documented or explained through comments. Also trigger when the user shares a file, module, class, or function and wants the reasoning, decisions, and intent made visible through human-voice commentary. This skill does not rewrite code. It illuminates it. Every comment written sounds like a thoughtful senior engineer speaking to the next developer who will read this — explaining not just what the code does, but why it does it that way, what was considered and rejected, and what the next person must not break.

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

16 rules. About 0 are common, 15 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈15

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

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.