google-docstring-assistant
Original:🇺🇸 English
Translated
Write Python docstrings following the Google Python Style Guide, using clear sections and examples.
11installs
Added on
NPX Install
npx skill4agent add dmitriiweb/extract-emails google-docstring-assistantTags
Translated version includes tags in frontmatterSKILL.md Content
View Translation Comparison →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 blocks with literal blocks (
Examples) for commands or code snippets.:: - Document module-level variables consistently (all in or inline), and list TODOs in a
Attributessection.Todo - See for full guidance and examples.
references/google_docstring_rules.md
Workflow
-
Choose sections
- Functions: include ,
Args, andReturnsas needed.Raises - Modules/classes: use and
Attributeswhen relevant; keep formatting consistent.Todo
- 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 with indented literal blocks for shell commands or code snippets.
Examples: - Include multi-line descriptions when needed; keep formatting readable.
- Use
Reference
- : full style description and examples.
references/google_docstring_rules.md