What problem does it solve? Choosing and migrating Python project tooling is error-prone: teams accumulate competing lockfiles, mismatched linters, and divergent local versus CI behavior. This Skill guides selection, configuration, and migration of Python toolchains while preserving working repository conventions. ## Core Features & Use Cases - Toolchain Selection: Recommends coherent stacks for environments and dependencies (uv, Poetry, pip-tools), packaging backends, linting and formatting (Ruff), type checking (Mypy, Pyright), and testing (pytest). - New-Project Baseline: Provides a concrete greenfield starting point with uv, Ruff, strict type checking, pytest with coverage floors, pre-commit, and PEP 621 metadata in pyproject.toml. - Migration Workflow: Defines an eight-step migration process that records current behavior, verifies candidates against official documentation, and removes obsolete configuration only after the new path is proven. - Use Case: When inheriting a repository with both Poetry and pip-tools lockfiles, use this Skill to identify the authoritative dependency source, plan a staged migration to a single lockfile, and verify local and CI builds stay reproducible. ## Quick Start Use the python-tooling skill to review this repository's pyproject.toml and CI configuration and recommend a coherent toolchain with a migration plan.
