python-style-guide

Automate Python code quality reviews and refactoring planning for typing, error handling, and module boundaries.

7|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/KentoShimizu/sw-agent-skills --skill python-style-guide-kentoshimizu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: python-style-guide
Source: https://github.com/KentoShimizu/sw-agent-skills/tree/main/skills/python-style-guide
Command: npx skills add https://github.com/KentoShimizu/sw-agent-skills --skill python-style-guide-kentoshimizu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) and references (resource) components.

What problem does it solve?

Python codebases often suffer from weak typing, inconsistent style, and brittle module boundaries, leading to maintenance pain and bugs.

Core Features & Use Cases

  • Establishes a consistent Python style guide, typing discipline, and refactoring strategies.
  • Applies during code reviews, onboarding, and ongoing maintenance to improve readability and reliability.

Quick Start

Apply the Python style guide to a codebase by running the recommended review checklist and refactor templates to align code with typing, error handling, and module boundaries.

Frequently Asked Questions about python-style-guide

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

FAQPage Schema
How do I enforce Python module boundaries and typing during a code review?

Automated Python code quality reviews enforce module boundaries by validating explicit type hints and boundary contracts. Applying a structured review checklist during refactoring identifies weak typing and brittle dependencies to drive consistent improvements.

What is the best way to plan refactoring for a Python codebase with weak typing?

The best way to plan Python refactoring is using structured templates that establish typing discipline and error handling strategies. These templates align code with strict module boundaries and apply a consistent style guide to improve readability and reliability.

Do I need explicit type hints to use a Python style guide for static analysis?

Yes, explicit type hints are required to use this Python style guide for static analysis. The review process depends on type hints and boundary contracts to evaluate code quality, enforce error handling, and drive structured refactoring improvements.

Can I use a Python style guide checklist for onboarding new developers?

Yes, you can use the Python style guide checklist during onboarding to establish consistent typing discipline and module boundaries. It provides a structured review process that helps new developers understand refactoring strategies and maintain code quality.

Why does Python static analysis fail to catch brittle module boundaries without contracts?

Python static analysis fails to catch brittle module boundaries without contracts because it requires explicit boundary definitions to validate dependencies. Enforcing boundary contracts through a structured review checklist ensures the static analysis can identify and correct weak typing.