What problem does it solve? Python repositories often mix system Python, pip, and ad hoc virtualenv commands, leading to broken environments, out-of-sync lockfiles, and inconsistent test or release runs. This Skill steers every setup, test, dependency, packaging, and release task toward uv and the repository's own defined entrypoints. ## Core Features & Use Cases - uv-first command selection: Prefers uv run, uv sync, and uv lock over system python, pip, or manual virtualenvs, and inspects pyproject.toml before choosing commands. - Repo-defined entrypoints: Favors [project.scripts] entrypoints, repo wrapper commands, AGENTS.md, and .github/github.json quality gates over generic pytest invocations. - Dependency and release discipline: Keeps pyproject.toml and uv.lock in sync, supports uv build and twine check for packaging, and never publishes or tags without explicit user request. - Use Case: When asked to run tests in a uv-managed repo, the agent checks the repo's documented commands and runs uv run test or the documented wrapper instead of guessing pytest against a system interpreter. ## Quick Start Use the python-uv-workflow skill to set up this repository and run its test suite with uv.
