What problem does it solve? Python projects often suffer from inconsistent dependency management: unpinned versions, mixed runtime and dev packages, missing lockfiles, and broken environments after fresh clones. This Skill defines a disciplined uv-based workflow so dependency changes are reproducible, correctly scoped, and consistently committed. ## Core Features & Use Cases - uv lifecycle commands: Covers add, remove, lock, sync, upgrade, and inspect operations with clear guidance on when to use each. - pyproject.toml conventions: Separates runtime dependencies from dev and optional dependency-groups, enforces minimum-version bounds instead of exact pins, and alphabetizes entries. - Lockfile discipline: Specifies what to commit (uv.lock, .python-version), what to exclude (.venv), and commit message conventions for dependency changes. - Troubleshooting and private indexes: Resolves common uv failures and configures alternate package indexes. - Use Case: You need to add polars to a project. The Skill guides you to run uv add polars, verify with uv tree, and commit both pyproject.toml and uv.lock with a conventional message. ## Quick Start Ask the assistant to add a new runtime dependency to your Python project using uv and update the lockfile accordingly.
