python-code-style

Enforce Python code style and documentation standards for naming, imports, and docstrings.

Updated Jan 24, 2026
One-click install
npx skills add https://github.com/amaozhao/MySkills --skill python-code-style-amaozhao
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: python-code-style
Source: https://github.com/amaozhao/MySkills/tree/main/skills/python-code-style
Command: npx skills add https://github.com/amaozhao/MySkills --skill python-code-style-amaozhao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes Python code style and documentation, reducing ambiguity and improving readability across projects.

Core Features & Use Cases

  • Naming conventions: CamelCase for classes, snake_case for functions, and UPPER_SNAKE_CASE for constants.
  • Docstring guidelines: Consistent module, class, and function docstrings following a chosen format.
  • Code patterns: Encourages Pythonic patterns and clean imports to improve maintainability.

Quick Start

Review a Python file and apply the style guide to naming, imports, and docstrings.

Frequently Asked Questions about python-code-style

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

FAQPage Schema
How do I enforce Python code style and docstring standards during code reviews?

To enforce Python code style during code reviews, apply standardized naming conventions like CamelCase for classes and snake_case for functions, while ensuring consistent docstring formats to improve readability and reduce ambiguity across projects.

What are the standard Python naming conventions for classes, functions, and constants?

Standard Python naming conventions dictate CamelCase for class names, snake_case for function and variable names, and UPPER_SNAKE_CASE for constants to maintain clear and predictable code readability.

What is the maximum line length recommended for Pythonic code patterns?

The recommended maximum line length for Pythonic code patterns is 88 characters, which balances readability with screen space utilization when standardizing code style across projects.

How do I write standard docstrings for Python modules and classes?

To write standard Python docstrings, follow consistent formatting guidelines for modules, classes, and functions, ensuring each component has clear documentation that reduces ambiguity and improves project maintainability.

Can I apply this Python style guide to clean up imports in existing projects?

Yes, you can apply this Python style guide to clean up imports in existing projects, as it encourages Pythonic patterns and clean imports to improve maintainability across both new code and legacy files.

Does this Python style guide require any external dependencies or linters?

No, this Python style guide does not require external dependencies or linters, serving as a standalone reference to standardize code style and documentation without additional environment setup.