python-guidelines

Review and refactor Python code against shared style and structure guidelines.

1|1|Updated May 1, 2026
One-click install
npx skills add https://github.com/funsaized/claude-and-codex-settings --skill python-guidelines-funsaized
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: python-guidelines
Source: https://github.com/funsaized/claude-and-codex-settings/tree/main/plugins/python-skills/skills/python-guidelines
Command: npx skills add https://github.com/funsaized/claude-and-codex-settings --skill python-guidelines-funsaized

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Consolidates Python coding standards into an accessible reference to reduce guesswork and inconsistency across projects.

Core Features & Use Cases

  • Idiomatic patterns and best practices for Python code organization, naming, and docstrings.
  • Guidance for integrating small, composable functions and avoiding over-abstracted wrappers.
  • Coding discipline: testing, simplicity, and readability as core constraints.
  • Use Case: When onboarding to a new codebase, align with a shared standard to accelerate contributors.

Quick Start

Review a Python module and refactor it to follow the guidelines for simplicity, readability, and idiomatic patterns.

Frequently Asked Questions about python-guidelines

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

FAQPage Schema
What are the best practices for writing idiomatic Python code?

Idiomatic Python best practices involve organizing code into small, composable functions, following explicit naming rules, and formatting docstrings to enforce readability and maintainability across teams.

How do I refactor Python code to improve readability and code quality?

Refactoring Python code for quality requires applying guidelines that simplify logic, remove over-abstracted wrappers, and enforce testing constraints to achieve a maintainable codebase.

How should Python docstrings be formatted for consistency?

Python docstrings should be formatted using explicit, structured rules from a shared set of guidelines, ensuring standardization across team contributions and improving module documentation.

When should I avoid over-abstraction in Python refactoring?

Avoid over-abstraction during Python refactoring when it creates unnecessary wrapper layers, preferring small, composable functions to maintain simplicity and foundational software engineering discipline.

Can I use these Python guidelines to onboard contributors to a new codebase?

Yes, you can use these Python guidelines to onboard contributors by having them review and refactor modules against the shared standard, accelerating alignment and consistency across projects.