python

Standardize Python workflows on uv for environments, dependencies, and execution.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/gakonst/dotfiles --skill python-gakonst
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: python
Source: https://github.com/gakonst/dotfiles/tree/main/.codex/skills/python
Command: npx skills add https://github.com/gakonst/dotfiles --skill python-gakonst

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes Python workflows around uv for environments, dependency resolution, and execution, avoiding pip/venv as the default.

Core Features & Use Cases

  • Env & deps with uv: create venv via uv and manage dependencies with uv.
  • Run & test with uv: run lint, type checks, and tests using uv.
  • CI parity: ensure CI uses uv-based steps for Python projects.

Quick Start

uv venv .venv && uv sync --frozen && uv run pytest

  • or - uv venv .venv; source .venv/bin/activate; uv sync uv lock

Frequently Asked Questions about python

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize Python workflows with uv instead of pip and venv?

Use uv to standardize Python workflows by replacing pip and venv with uv venv for environment creation, uv add for dependency management, uv sync for lockfile synchronization, and uv run for executing commands. This ensures consistent, reproducible workflows across local development and CI.

Can I use uv to run pytest, mypy, and ruff without activating a virtual environment?

Yes. Run uv run pytest, uv run mypy, and uv run ruff to execute testing, type checking, and linting directly through uv without manually activating a virtual environment, maintaining isolation and consistency.

How do I set up a new Python project with uv and lock dependencies?

Create an isolated environment with uv venv .venv, sync dependencies using uv sync --frozen, and pin versions with uv lock. This establishes a reproducible project setup with all dependencies locked and ready to run.

What's the best way to ensure CI parity when using uv for Python projects?

Configure CI to use the same uv-based commands: uv venv, uv sync, and uv run for pytest, ruff, and mypy. This guarantees local and CI environments behave identically, eliminating environment-related failures.

Do I need to manage system site-packages when using uv for isolated environments?

No. uv venv creates isolated environments that exclude system site-packages by default, ensuring dependencies are resolved only from uv-managed lockfiles without interference from system Python packages.