standardizing-python

Enforce Python linting, typing, and naming conventions with Ruff and MyPy.

1|Updated Jan 6, 2026
One-click install
npx skills add https://github.com/outcomeeng/claude --skill standardizing-python-outcomeeng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: standardizing-python
Source: https://github.com/outcomeeng/claude/tree/main/plugins/python/skills/standardizing-python
Command: npx skills add https://github.com/outcomeeng/claude --skill standardizing-python-outcomeeng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Python code standards enforced across all skills. Loaded by other skills, not invoked directly.

Core Features & Use Cases

  • Ruff rules enforcement, including complete type annotations and naming conventions, to maintain consistent Python code quality.
  • Shared standards reference used by other Python skills for coding, testing, and reviewing.
  • Use case: ensure any newly created Python skill adheres to the same linting and typing requirements across projects.

Quick Start

Apply these standards to new Python code and reviews to ensure compliance from the outset.

Frequently Asked Questions about standardizing-python

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

FAQPage Schema
How do I enforce Python coding standards across multiple projects?

To enforce Python coding standards across multiple projects, you apply shared rules requiring complete type annotations, Ruff linting, and MyPy static analysis to ensure consistent code quality and review workflows.

How do I require complete type annotations for all Python functions?

Requiring complete type annotations for all Python functions involves applying shared static analysis guidelines and MyPy configurations that enforce typing rules during code generation and review.

Can I use Ruff and MyPy together for Python linting and type checking?

You can use Ruff and MyPy together for Python linting and type checking by loading shared standards that enforce naming conventions and static analysis guidelines across your Python-based skills.

What's the best way to maintain consistent Python code quality during code reviews?

The best way to maintain consistent Python code quality during reviews is to apply standardized Ruff rules and type annotation checks from the outset, ensuring all functions adhere to shared linting and typing requirements.

How do I apply consistent naming conventions and static analysis to Python code?

To apply consistent naming conventions and static analysis to Python code, you enforce Ruff rules and shared coding standards that validate type annotations and linting guidelines across all Python skills.

Do I need complete type annotations on all functions to pass Python static analysis?

Yes, complete type annotations on all functions are required to pass the Python static analysis guidelines enforced by MyPy and Ruff rules within this shared coding standards workflow.