docstring
Skill0 starsChanged 2 months agoLicence not identifiedView on GitHub
MUST be used whenever the user asks to add, generate, or fill in missing docstrings/doc-comments for a file or symbol. Always invoke this instead of writing docstrings yourself.
8 other projects use a version of this.
Adopted by
Most recently taken up by
- pipecat-ai/pipecattheir own version, first seen Oct 8, 2026
- pytorch/pytorchtheir own version, first seen Oct 8, 2026
- llp42/claude-skillsword for word, first seen Sep 9, 2026
- NVIDIA/structured-data-modelstheir own version, first seen Jul 29, 2026
- Jinbae10/skillstheir own version, first seen Jul 7, 2026
- Pradnyeshp/Claude-Skillstheir own version, first seen Jul 6, 2026
Other versions8 projects use a version of this.
Word for word · 1
- llp42/claude-skills★ 0100% same
Edited · 0
None found.
Wrote their own version · 7
- pytorch/pytorch★ 105ksame name
- pipecat-ai/pipecat★ 17ksame name
- NVIDIA/structured-data-models★ 473same name
- nilecui/SkillsBase★ 27same name
- Pradnyeshp/Claude-Skills★ 2same name
- Jinbae10/skills★ 0same name
- sissc0731/claude-code-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository15 other files it gives its agents.
- changelogSkill
- commitSkill
- csv-summarySkill
- deps-doctorSkill
- deps-summarySkill
- doc-formatSkill
- env-lintSkill
- flaky-detectorSkill
- go-standardsSkill
- grillingSkill
- grill-meSkill
- lint-fixSkill
- pr-storytellerSkill
- standup-genSkill
- test-gapSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 7 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 7 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.
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.