mcpField
E
environment-triage

environment-triage

github.com/parcadeiDevelopment3.9k480 installsUpdated 39w ago
Repository

About environment-triage

environment-triage is a troubleshooting skill for developers investigating Python installation issues. It focuses on checking the interpreter actually selected by uv or a virtual environment before debugging further.

Key features

  1. 01Check the Python version selected by uv
  2. 02Inspect the .python-version setting
  3. 03Verify package installation
  4. 04Update the interpreter and rebuild the environment

Use cases

  1. 01Dependencies missing after uv sync
  2. 02Imports failing after pip install
  3. 03Optional dependencies gated by Python version

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/parcadei/continuous-claude-v3 --skill environment-triage

After installing, type/environment-triagein Claude Code to confirm it loaded.

Details

From the project README

Environment Triage

When uv sync or pip install behaves unexpectedly, check the actual interpreter.

Pattern

System Python is not authoritative if uv/venv selects a different interpreter.

DO

# What uv ACTUALLY uses
uv run python --version

# What's pinned (this controls uv)
cat .python-version

# Confirm package is installed
uv pip show <package>

# Confirm import works in uv context
uv run python -c "import <package>; print(<package>.__version__)"

Common Fix

If optional deps require Python 3.12+ but .python-version is 3.11:

echo "3.13" > .python-version
rm -rf .venv && uv venv && uv sync --all-extras

DON'T

  • Trust python3 --version when using uv
  • Assume install succeeded without verifying import
  • Debug further before checking interpreter version

Source Sessions

  • 2243c067: symbolica-agentica skipped due to python_version >= 3.12 marker, but uv was using 3.11
  • 4784f390: agentica import failures traced to wrong interpreter

Comments

Markdown supported