auto-docstring-rules

Enforce Google-style docstring conventions for Python code.

Updated Feb 26, 2026
One-click install
npx skills add https://github.com/Thanhhuong0209/DLT-Normalization --skill auto-docstring-rules
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auto-docstring-rules
Source: https://github.com/Thanhhuong0209/DLT-Normalization/tree/main/.claude/skills/auto-docstring-rules
Command: npx skills add https://github.com/Thanhhuong0209/DLT-Normalization --skill auto-docstring-rules

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that Python code adheres to consistent and high-quality docstring standards, improving code readability and maintainability.

Core Features & Use Cases

  • Enforces Google Style: Guides developers to use the correct Google docstring format for functions, classes, and fields.
  • Promotes Clarity: Encourages concise descriptions and appropriate use of Args, Returns, Yields, and Raises sections.
  • Use Case: When reviewing a pull request, use this Skill to automatically check if new or modified docstrings follow the established conventions, preventing stylistic inconsistencies.

Quick Start

Use the auto-docstring-rules skill to review the docstrings in the provided Python code file.

Frequently Asked Questions about auto-docstring-rules

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce Python docstring conventions in my code?

You can enforce Python docstring conventions by applying rules that check for Google style format, ensuring concise descriptions and proper use of Args, Returns, Yields, and Raises sections in functions and classes.

What is the Google style guide for Python docstrings?

The Google style guide for Python docstrings is a format standard that requires concise short-form and full-form descriptions, specific field docstrings, and structured sections like Args, Returns, Yields, and Raises to improve code readability.

How do I check docstrings for anti-patterns during a code review?

To check docstrings for anti-patterns during code review, validate the modified function signatures and class definitions against established Google style guidelines to identify and prevent stylistic inconsistencies.

Can I use this to review field docstrings and function signatures?

Yes, you can use this to review field docstrings and function signatures, as it specifically applies to writing or modifying these elements to ensure they adhere to the required dlt docstring conventions.

What are common anti-patterns when writing Python docstrings?

Common anti-patterns when writing Python docstrings include inconsistent formatting, missing Args or Returns sections, and overly verbose descriptions that deviate from the established Google style short-form and full-form guidelines.