as-python-docstrings

To generate Python docstrings, you provide the file path and symbol name, and the skill automates documentation of classes, methods, functions, and modules by describing their purpose, inputs, outputs, and side effects.

Auditing and rewriting legacy Python docstrings involves applying concise guidelines to refine existing documentation, improving clarity and coverage to establish a documentation contract that aids maintenance and testing.

Yes, you can document code without changing behavior, as the process strictly avoids code changes and focuses entirely on refining user-facing interface documentation and clarifying the contract.

Automated docstring generation works for both new code and legacy modules, applying concise guidelines that prioritize user-facing purpose, contract, and minimalism across editing and auditing tasks.

Python docstrings should include a symbol's purpose, inputs, outputs, and side effects, ensuring consistent user-facing API documentation and code clarity while maintaining a minimalist style.

You should not use automated docstring generation when you need to change code behavior or logic, as the skill explicitly avoids code changes and focuses solely on interface documentation and style refinement.