doc-generator
Skill3 starsChanged 9 months agoMITView on GitHub
Generate API documentation, docstrings, and technical documentation from code. Use when the user wants to document functions, create API docs, or generate documentation from code.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- iberi22/skillstheir own version, first seen Oct 15, 2026
- weiweimhy/agent-skillstheir own version, first seen Jul 1, 2026
- 0chandansharma/claude-skillstheir own version, first seen May 22, 2026
- vikisingh23/neuraforge-aitheir own version, first seen May 4, 2026
- wenboxia/doc-generatortheir own version, first seen Apr 16, 2026
- z-waterking/claude-skillstheir own version, first seen Apr 4, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- vikisingh23/neuraforge-ai★ 4same name
- wenboxia/doc-generator★ 1same name
- 0chandansharma/claude-skills★ 0same name
- iberi22/skills★ 0same name
- weiweimhy/agent-skills★ 0same name
- z-waterking/claude-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 repository5 other files it gives its agents.
- changelog-generatorSkill
- code-reviewSkill
- commit-messageSkill
- refactor-assistantSkill
- test-generatorSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
4
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
- Distinctive: line 57
Run validation after generating docs:
- Distinctive: line 81
Verify examples are runnable
- Distinctive: line 82
Check for spelling/grammar
- Distinctive: line 83
Ensure consistency across module
“Common” is measured: kept by at least 6 in 10 of the 5 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.
Files
Documentation Generator
Generate clear, consistent documentation for Python code.
Documentation Workflow
Progress:
- [ ] Step 1: Analyze code structure
- [ ] Step 2: Generate docstrings
- [ ] Step 3: Validate documentation
- [ ] Step 4: Fix validation errors
- [ ] Step 5: Final reviewStep 1: Analyze Code
Identify what needs documentation:
- Public functions and methods
- Classes and their attributes
- Module-level docstrings
- Complex logic blocks
Step 2: Generate Docstrings
Use Google-style docstrings:
def fetch_user(user_id: int, include_profile: bool = False) -> User:
"""Fetch a user from the database.
Args:
user_id: The unique identifier of the user.
include_profile: Whether to load the full profile. Defaults to False.
Returns:
The User object with requested data.
Raises:
UserNotFoundError: If no user exists with the given ID.
DatabaseError: If the database connection fails.
Example:
>>> user = fetch_user(123)
>>> print(user.name)
'John Doe'
"""Step 3: Validate Documentation
Run validation after generating docs:
python scripts/validate_docs.py src/Expected output:
OK- All docstrings valid- Error list - Issues to fix
Step 4: Fix Validation Errors
Common issues:
| Error | Fix |
| Missing Args | Add missing parameter docs |
| Wrong type | Update type annotation |
| Missing Returns | Add return description |
| Missing Raises | Document exceptions |
Loop back to Step 3 until validation passes.
Step 5: Final Review
- Verify examples are runnable
- Check for spelling/grammar
- Ensure consistency across module
Templates
See templates/ for:
module.md- Module docstring templateclass.md- Class documentation templateapi.md- REST API documentation template
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.

