no-added-comments
Skill1 starsChanged 19 days agoMITView on GitHub
Use whenever you write or change code. Keeps the diff free of comments you added and leaves existing comments as they were.
In this repository17 other files it gives its agents.
- broooooSkill
- did-we-break-itSkill
- finish-the-prSkill
- fix-it-properlySkill
- just-tell-meSkill
- lets-build-pyramidsSkill
- next-time-fasterSkill
- onmywatchSkill
- plan-the-big-oneSkill
- sharpenSkill
- show-meSkill
- statechartSkill
- talk-is-cheapSkill
- trust-issuesSkill
- trust-me-broSkill
- walk-me-throughSkill
- you-get-meSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
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
- Distinctive: line 9
When you change code, do not add comments.
- Distinctive: line 13
No explanations of why a line exists.
- Distinctive: line 14
No section separators in tests.
- Distinctive: line 15
No notes inside assertions that restate the reason for the check.
- Distinctive: line 16
No edits to existing comments or doc blocks.
- Distinctive: line 18
Put the reasoning in your reply to the user, not in the diff.
- Distinctive: line 22
If a constraint really must be recorded, prefer a name, a type or a test that enforces it over a comment that describes it.
≈ “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.
Files
no-added-comments
When you change code, do not add comments.
Scope: $ARGUMENTS. If that is empty, every change you make in this session.
- No explanations of why a line exists.
- No section separators in tests.
- No notes inside assertions that restate the reason for the check.
- No edits to existing comments or doc blocks. Leave their wording as it was.
Put the reasoning in your reply to the user, not in the diff.
Touch an existing comment only when the code it describes is removed.
If a constraint really must be recorded, prefer a name, a type or a test that enforces it over a comment that describes it.
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
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.