Backend Python Standards

Standardize backend Python workflows with uv, pytest, ruff, and mypy.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/DennisToma/repo_example --skill backend-python-standards-dennistoma
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Backend Python Standards
Source: https://github.com/DennisToma/repo_example/tree/main/.claude/skills/backend-python-standards
Command: npx skills add https://github.com/DennisToma/repo_example --skill backend-python-standards-dennistoma

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill standardizes Python development workflows across projects by enforcing consistent tooling and code quality practices, reducing configuration drift and cognitive load for teams.

Core Features & Use Cases

  • Enforces the use of uv for package operations, pytest for testing, ruff for formatting and linting, and mypy or basedpyright for type checking.
  • Promotes self-documenting code with concise docstrings, clean imports, and clear type hints to improve maintainability and onboarding.
  • Use Case: When starting a new Python backend service or refactoring an existing module, apply these standards to ensure consistent tooling, tests, and documentation from day one.

Quick Start

  • Ensure uv, pytest, ruff, and mypy are installed and configured.
  • Run: uv run pytest to execute tests, uv run ruff to lint/format, and uv run mypy for type checks.
  • Add/update docstrings and import order in newly touched files to align with the standards.

Frequently Asked Questions about Backend Python Standards

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

FAQPage Schema
How do I standardize Python tooling for backend services?

To standardize Python tooling for backend services, enforce uv for package operations, pytest for testing, ruff for linting and formatting, and mypy or basedpyright for type checking across all projects. This reduces configuration drift and cognitive load for teams.

What's the best way to enforce consistent Python code quality across projects?

The best way to enforce consistent Python code quality is by standardizing tooling workflows with ruff for formatting, mypy for type checks, and pytest for tests, while emphasizing concise docstrings and clean imports to improve maintainability and onboarding.

How do I run Python linting, type checking, and tests using uv?

Run Python linting, type checking, and tests using uv by executing `uv run ruff` for linting and formatting, `uv run mypy` for type checks, and `uv run pytest` to execute tests within your standardized Python development workflow.

Does this Python standardization workflow support basedpyright for type checking?

Yes, this Python standardization workflow supports basedpyright for type checking alongside mypy. You can use either tool to enforce strict type hints and self-documenting code across your backend Python services and libraries.

When do I need to standardize Python development workflows with uv and ruff?

You need to standardize Python development workflows with uv and ruff when starting a new backend Python service or refactoring an existing module, ensuring consistent tooling, tests, and documentation from day one to reduce configuration drift.