What problem does it solve? Python repositories accumulate inconsistent tooling choices over time, and changing or modernizing them risks breaking builds, CI, and contributor workflows. This Skill guides safe configuration and maintenance of project-level Python tooling without disrupting established setups. ## Core Features & Use Cases - Respect Existing Toolchains: Inspects pyproject.toml, lockfiles, CI, and contributor docs, then continues using the repository's configured tools instead of replacing them. - Modern Project Setup: For new or deliberately modernized projects, recommends uv for environments and dependencies, Ruff for linting and formatting, ty for type checking, and pytest for tests, with canonical configuration in pyproject.toml. - Safe Change Management: Separates tool migrations from feature work, verifies lock consistency, clean-environment installs, checks, tests, and builds, and prefers trusted publishing with dry runs for releases. - Use Case: When asked to lint or type-check specific files in an existing repository, it scopes the repository's configured commands to those files and reports gaps rather than silently adding new tools. ## Quick Start Ask the assistant to set up tooling for a new Python project or to run the repository's configured lint, format, and type checks on specific files.