google-docstring-assistant
Write Python docstrings following the Google Python Style Guide, using clear sections and examples.
$ インストール
git clone https://github.com/dmitriiweb/extract-emails /tmp/extract-emails && cp -r /tmp/extract-emails/.codex/skills/google-docstring-assistant ~/.claude/skills/extract-emails// tip: Run this command in your terminal to install the skill
SKILL.md
name: google-docstring-assistant description: Write Python docstrings following the Google Python Style Guide, using clear sections and examples.
Google Docstring Assistant
Quick start
- Write docstrings using the Google Python Style Guide structure (Args, Returns, Raises, Examples, Attributes, etc.).
- Keep sections as headers followed by indented blocks; break sections by resuming unindented text.
- When types are annotated in code, omit them in docstrings unless clarity is improved.
- Use
Examplesblocks with literal blocks (::) for commands or code snippets. - Document module-level variables consistently (all in
Attributesor inline), and list TODOs in aTodosection. - See
references/google_docstring_rules.mdfor full guidance and examples.
Workflow
-
Choose sections
- Functions: include
Args,Returns, andRaisesas needed. - Modules/classes: use
AttributesandTodowhen relevant; keep formatting consistent.
- Functions: include
-
Write clearly
- One docstring per object; keep it concise and informative.
- Use indentation under each section header; separate sections by returning to unindented text.
- Prefer Google-style wording; avoid duplicating annotated types unless helpful.
-
Examples and scripts
- Use
Examples:with indented literal blocks for shell commands or code snippets. - Include multi-line descriptions when needed; keep formatting readable.
- Use
Reference
references/google_docstring_rules.md: full style description and examples.
Repository

dmitriiweb
Author
dmitriiweb/extract-emails/.codex/skills/google-docstring-assistant
106
Stars
38
Forks
Updated6d ago
Added1w ago