migrate-pip-to-uv

Automate Python monorepo dependency migration from pip/pip-tools to uv.

1|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/squirrel289/pax --skill migrate-pip-to-uv
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate-pip-to-uv
Source: https://github.com/squirrel289/pax/tree/main/skills/tools/migrate-pip-to-uv
Command: npx skills add https://github.com/squirrel289/pax --skill migrate-pip-to-uv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates migrating Python monorepo dependency management from pip/pip-tools to uv, including creating pyproject.toml, generating uv.lock, and updating workflows for universal, locked, multi-group dependencies.

Core Features & Use Cases

  • Convert legacy requirements files to uv projects with pyproject.toml and universal lockfile generation.
  • Migrate development, testing, docs, and platform-specific dependency groups.
  • Update project workflows to use uv commands and environments for reliable builds.

Quick Start

Run migrate-pip-to-uv in your repository root to start the migration workflow.

Frequently Asked Questions about migrate-pip-to-uv

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

FAQPage Schema
How do I migrate a Python monorepo from pip to uv?

Migrating a Python monorepo from pip to uv involves analyzing existing requirements files, initializing a uv project, importing dependencies, and generating a universal uv.lock file along with updated workflows.

How does uv handle platform-specific dependencies in a monorepo?

uv handles platform-specific dependencies in a monorepo by generating a universal lockfile that resolves and locks constraints across Windows, Linux, and macOS within the uv.lock file.

Can I migrate multiple dependency groups like dev and docs to uv?

Yes, you can migrate multiple dependency groups including base, dev, and docs to uv by defining them in the generated pyproject.toml and syncing the environments accordingly.

What is the best way to convert requirements files to a uv project?

The best way to convert legacy requirements files to a uv project is to analyze the existing pip-tools setup, initialize the uv project, import dependencies into pyproject.toml, and lock them for reliable builds.

Does migrating to uv update my project workflows automatically?

Yes, migrating to uv updates project workflows automatically by replacing legacy pip commands and environments with uv commands to ensure reliable and locked builds.

What are the limitations of migrating pip-tools to uv in a monorepo?

Migrating pip-tools to uv in a monorepo requires handling complex dependency groups and platform-specific constraints, meaning the lockfile generation must account for universal resolution across all target operating systems.