mcpField
U
uv

uv

github.com/jamie-bitflightDevelopment35 installs
Repository

About uv

A policy skill for Python development with uv, intended for workflows that follow shared engineering standards. It sets rules for dependency management, script execution, and TOML file handling, and points to external uv references.

Key features

  1. 01Align Python architecture, typing, and testing
  2. 02Use uv add, uv sync, and uv run
  3. 03Specify a PEP 723 script shebang
  4. 04Require text mode with tomlkit
  5. 05Link to uv docs and migration guides

Use cases

  1. 01Add or synchronize dependencies in a Python project
  2. 02Run Python code and scripts with uv
  3. 03Read or write TOML configuration using tomlkit

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/jamie-bitflight/claude_skills --skill uv

After installing, type/uvin Claude Code to confirm it loaded.

Details

From the project README

uv — Policy

Precedence: this policy (below) > astral:uv (if installed) / live docs.astral.sh for command syntax, migration tables, and general usage (not duplicated here).

Policy

  • Follow python-engineering:standards-for-python-development for shared architecture, typing, testing, and CLI rules.
  • Use uv add / uv sync / uv run for all Python work — never uv pip install, uv venv, or source .venv/bin/activate. A uv.lock-managed project with PEP 723 scripts never needs the pip-compatible lane Astral documents.
  • Portable PEP 723 script shebang: #!/usr/bin/env -S uv run --quiet --script. Omit --active unless the script is intentionally coupled to the caller's activated virtual environment.
  • Use text mode ('r'/'w') with tomlkit, never binary mode ('rb'/'wb') — binary mode returns bytes, which tomlkit cannot parse or write.

External Resources (if astral:uv isn't installed)

Comments

Markdown supported