// UV command automation and project lifecycle management patterns powered by the uv-mcp server
Python import style guidelines for absolute and relative imports
Python naming conventions for variables, constants, files, and directories
Python pathlib usage guidelines for file and directory operations
Python refactoring triggers and guidelines for code size limits
UV command-line usage patterns for Python project management
Universal coding principles and best practices for maintainable software
| name | uv-mcp |
| description | UV command automation and project lifecycle management patterns powered by the uv-mcp server |
| license | MIT |
| compatibility | opencode |
| metadata | {"related_python_guidelines":"For general Python development standards","related_python_cli":"For CLI scaffolding patterns","related_mcp_servers":"For MCP integration best practices"} |
Describe how to steer the uv-mcp server so natural language requests become precise uv workflows. This skill focuses on diagnosing environments, managing dependencies, controlling Python runtimes, and building artifacts with uv while keeping the workspace healthy.
| Intent | Tool | What Happens |
|---|---|---|
| Diagnose failures or missing environments | diagnose_environment | Confirms pyproject.toml, virtualenv presence, lock sync status, and reports remediation steps. |
| Repair broken setups | repair_environment | Creates .venv, installs Python, and syncs dependencies automatically. |
| Verify/install uv itself | check_uv_installation, install_uv | Checks uv availability and returns platform-specific install steps when missing. |
> "Diagnose the environment"
# Use output to confirm pyproject + venv state
> "Repair the environment"
# Follow-up diagnostics ensure issues are resolved
| Scenario | Tool | Notes |
|---|---|---|
| Add/remove libraries | add_dependency, remove_dependency | Supports --dev, optional dependency groups, and updates both config + env. |
Keep env aligned with uv.lock | sync_environment | Syncs or upgrades locked versions; run after lockfile updates. |
| Inspect or refresh packages | check_outdated_packages, show_package_info | Surfaces available upgrades and in-depth metadata for any package. |
list_dependencies: Lists installed packages; request tree mode for transitive view.analyze_dependency_tree: Visualizes dependency graph depth to spot heavy branches before refactors.| Action | Tool | Guidance |
|---|---|---|
| List installed interpreters | list_python_versions | Shows versions uv already manages. |
| Install new interpreter | install_python_version | Downloads and activates the requested Python release. |
| Pin project runtime | pin_python_version | Updates .python-version to keep CI/CD aligned. |
init_project: Scaffold a fresh uv-enabled project, ideal for greenfield work.export_requirements: Emit requirements.txt for platforms that expect pip-compatible manifests.| Need | Tool | Tips |
|---|---|---|
| Create wheels/sdists | build_project | Choose wheel-only or sdist-only, customize output dir, capture artifact paths. |
| Refresh lockfile without installing | lock_project | Useful after manual pyproject.toml edits or before committing dependency changes. |
| Clear uv cache | clear_cache | Fixes checksum mismatches or frees disk space; target entire cache or a single package. |
diagnose_environmentrepair_environmentdiagnose_environment again.clear_cache → lock_project → sync_environment.error, error_code, suggestion). Echo them in summaries so humans know the auto-remediation path.install_uv.sync_environment.clear_cache then lock_project and sync_environment.clear_cache for that package and re-sync.requirements.txt exports.add_dependency / lock_project call should be followed by sync_environment to keep .venv aligned.pin_python_version once a runtime is validated by CI.clear_cache when checksum or corruption errors show up, then re-sync immediately.build_project, record the returned artifact list (wheel + sdist paths) in release notes.python-guidelines: Apply linting/testing standards after uv-mcp modifies dependencies.python-cli: Use init_project + dependency adds to scaffold CLIs rapidly.mcp-servers: Document uv-mcp availability in .vscode/mcp.json and keep tool lists lean.Use this skill whenever the uv-mcp server is the fastest path to maintaining healthy uv environments without leaving the IDE context.