uv-debug

Diagnose uv build-cache and installation discrepancies in Python packaging.

7|Updated Oct 10, 2025
One-click install
npx skills add https://github.com/WarrenZhu050413/Warren-Claude-Code-Plugin-Marketplace --skill uv-debug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: uv-debug
Source: https://github.com/WarrenZhu050413/Warren-Claude-Code-Plugin-Marketplace/tree/main/claude-context-orchestrator/skills/uv-debug
Command: npx skills add https://github.com/WarrenZhu050413/Warren-Claude-Code-Plugin-Marketplace --skill uv-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill eliminates the frustration of Python package installation issues, automatically detecting and resolving common uv problems that waste developer time.

Core Features & Use Cases

  • Systematic Troubleshooting: Provides step-by-step workflows for common uv installation and build cache problems.
  • Installation Mode Management: Automatically identifies and switches between production, editable, and local installation modes.
  • Use Case: Imagine you've updated your Python package but changes aren't appearing in the installed version. Use this Skill to instantly diagnose whether it's a stale build cache, installation mode confusion, or dependency issues.

Quick Start

Use the uv-debug skill to diagnose why my code changes aren't appearing after running 'uv tool install .'

Frequently Asked Questions about uv-debug

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

FAQPage Schema
Why aren't my code changes appearing after running uv tool install?

Code changes often don't appear due to stale build caches or installation mode mismatches. Diagnose whether you're using editable mode (reflects live changes) versus production mode (requires reinstall), inspect your build/ and dist/ artifacts, and clear the cache before reinstalling to force a fresh build.

How do I fix installation discrepancies between uv run and global installs?

Installation discrepancies occur when uv run and global environments reference different package versions or build artifacts. Verify your install mode, check egg-info/RECORD files to confirm artifact locations, and use force-rebuild workflows—clear cache, clean builds, and forced reinstall—to synchronize both environments.

What should I do when new Python modules aren't discovered after installation?

Missing module discovery typically signals stale build artifacts or incorrect entry points. Validate artifact locations in build/ and dist/, inspect egg-info metadata, confirm your installation mode (editable versus production), and execute a force-rebuild sequence to regenerate package metadata and entry points.

How can I troubleshoot build cache problems in Python package workflows?

Build cache issues stem from stale artifacts across editable, production, and local environments. Systematically inspect egg-info/RECORD, verify installation modes, validate artifact locations, and apply reproducible force-rebuild commands—clear cache, clean builds, and forced reinstall—to eliminate inconsistencies.

When should I use editable versus production install mode with uv?

Use editable mode during development to reflect code changes immediately without reinstalling; use production mode for stable deployments. Mismatching modes causes code updates to vanish or dependencies to diverge. Diagnose your current mode and switch deliberately based on your workflow stage.

Do I need to manually clear the build cache, or can uv automate it?

Manual cache clearing is necessary to resolve persistent installation issues. Guided force-rebuild workflows include explicit cache-clearing steps followed by clean builds and forced reinstalls to guarantee fresh artifacts and eliminate stale build problems.