uv workflows for Python — dependencies, virtualenvs, PEP 723 scripts, Python version management, CI, and Docker. Use when working on Python packaging/deps/tooling, writing GitHub Actions for Python projects, or building Docker images for Python apps.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Assumption: uv is installed and on PATH (uv --version to confirm; if missing, halt and report).
Version pins below were current 2026-07-05 — verify before relying on them.
uv init myproj # create pyproject.toml + .venv
cd myproj
uv add ruff pytest httpx # fast resolver + lock update
uv run pytest -q # run tests in project venv
uv lock # refresh uv.lock (if needed)
uv sync --locked # reproducible install (CI-safe)
uv run hello.py # zero-dep script, auto-env
uv add --script hello.py rich # embeds dep metadata in the script
uv run --with rich hello.py # transient deps, no state
uvx ruff check . # ephemeral run
uv tool install ruff # user-wide persistent install
uv tool list # audit installed CLIs
uv tool update --all # keep them fresh
uv python install 3.12 3.13
uv python pin 3.13 # writes .python-version
uv run --python 3.12 script.py
uv venv .venv
source .venv/bin/activate
uv pip install -r requirements.txt
uv pip sync -r requirements.txt # deterministic install
| Env Var | Purpose | Typical value |
|---|---|---|
UV_CONCURRENT_DOWNLOADS | saturate fat pipes | 16 or 32 |
UV_CONCURRENT_INSTALLS | parallel wheel installs | CPU cores |
UV_OFFLINE | cache-only mode | 1 |
UV_INDEX_URL | internal mirror | https://… |
UV_PYTHON | pin interpreter in CI | 3.13 |
uv cache dir && uv cache size # show path + size
uv cache clean # wipe wheels & sources
name: tests
on: [push]
jobs:
pytest:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: astral-sh/setup-uv@v8.2.0 # immutable releases since v8.0.0 — moving tags like @v8 do NOT exist; pin the full version
- run: uv python install # obeys .python-version
- run: uv sync --locked
- run: uv run pytest -q
# Build stage
FROM ghcr.io/astral-sh/uv:python3.13-bookworm-slim AS builder
WORKDIR /app
# Deps first for layer caching; code after
COPY pyproject.toml uv.lock ./
RUN uv sync --frozen --no-cache --no-dev
# Runtime stage
FROM debian:bookworm-slim
COPY --from=ghcr.io/astral-sh/uv:latest /uv /bin/uv
RUN useradd --create-home --shell /bin/bash app
WORKDIR /app
COPY --from=builder /app/.venv /app/.venv
COPY --chown=app:app . .
USER app
ENV PATH="/app/.venv/bin:$PATH"
CMD ["uv", "run", "python", "-m", "myapp"]
Tips: copy pyproject.toml + uv.lock before app code (layer caching); --frozen honors the lockfile exactly; --no-cache keeps the image lean; --no-dev skips dev deps; set PATH so the venv is active.
| Legacy | Replacement |
|---|---|
python -m venv | uv venv |
pip install | uv pip install |
pip-tools compile | uv lock |
pipx run | uvx |
poetry add | uv add |
pyenv install | uv python install |
| Symptom | Resolution |
|---|---|
Python X.Y not found | uv python install X.Y or set UV_PYTHON |
| C-extension build errors | unset UV_NO_BUILD_ISOLATION |
| Need a fresh env | uv cache clean && rm -rf .venv && uv sync |
| Still stuck | RUST_LOG=debug uv ... |
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use when evaluating, designing, or pressure-testing the business model of an AI agent product. Triggers on "agent business model", "agent economics", "agent canvas", "evaluate agent product", "agent pricing", "agent unit economics", "agentic business", "AI agent company", "agent cost structure".
The English summary is being prepared. Showing the original description.
Create user-facing App Store release notes by collecting and summarizing all user-impacting changes since the last git tag (or a specified ref). Use when asked to generate a comprehensive release changelog, App Store "What's New" text, or release notes based on git history or tags.
The English summary is being prepared. Showing the original description.
Use when someone wants to launch a content brand from scratch on any platform. Triggers on "launch a channel", "start a YouTube channel", "build a podcast", "start a newsletter", "content brand", "creator launchpad", "build my audience", "start creating content", "grow on TikTok", "start a blog".
The English summary is being prepared. Showing the original description.
Use when you have an existing pipeline DOT file that needs review, fixing, or validation. Use when validation produces warnings or errors, when a DOT file was hand-written or generated by another tool, or when you want to verify a pipeline covers 100% of a spec before running it.
The English summary is being prepared. Showing the original description.
Use when you want to build a project but don't have a spec yet and need to brainstorm the idea into a design doc structured for pipeline DOT generation. Use when starting from a vague idea, project concept, or feature request that needs to become a headless autonomous build pipeline.
The English summary is being prepared. Showing the original description.
Use when you have a spec, design doc, structured plan, or prompt_plan and need to generate a pipeline Graphviz DOT file for headless autonomous building. The agent reads the spec, extracts build pipeline phases, determines tech stack, asks about human gates and model preferences, generates a validated DOT digraph with rich self-contained prompts, and saves it to the project root. Handles any language or framework.
The English summary is being prepared. Showing the original description.