القائمة
Use when running Python, installing Python packages, creating virtualenvs, or executing Python CLI tools - mandates uv/uvx over direct python/pip/pipx/venv calls when uv is installed, and gives the drop-in command mappings
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | howto-uv |
| description | Use when running Python, installing Python packages, creating virtualenvs, or executing Python CLI tools - mandates uv/uvx over direct python/pip/pipx/venv calls when uv is installed, and gives the drop-in command mappings |
uv is a fast, reproducible Python package and project manager. When uv is
on PATH, prefer it over direct python, pip, pipx, and venv calls. It
resolves and caches dependencies deterministically, manages the interpreter,
and makes ad-hoc tool runs reproducible without polluting the global
environment.
Check availability with command -v uv. If uv is not installed, fall back to
python/pip as usual - this guidance applies only when uv is present.
| Instead of | Use |
|---|---|
python script.py | uv run script.py |
python -m module | uv run python -m module |
python -c '...' | uv run python -c '...' |
python (REPL) | uv run python |
pip install X | uv pip install X (ad hoc) or uv add X (project dep) |
python -m pip install X | uv pip install X |
python -m venv .venv | uv venv .venv |
pipx run X | uvx X |
pipx install X | uv tool install X |
pip-compile / freeze | uv lock / uv pip compile |
uv run ensures the project's locked dependencies are present and uses the
pinned interpreter before executing - no manual activate step, no stale venv.uvx TOOL runs a CLI tool in an ephemeral, cached environment. Reach for it
for one-off tools (uvx ruff check, uvx black ., uvx httpie) instead of
globally installing them.uv add (records the dep in pyproject.toml and the
lockfile) over uv pip install (which mutates the environment without
recording intent).python --version / python -V capability probes are fine as-is.uv is absent,
follow the repo. Do not introduce uv where the project does not use it.uv run app.py # run a script with project deps
uv run pytest # run an installed dev tool
uvx ruff check . # run a tool without installing it
uv add httpx # add a dependency to the project
uv pip install requests # ad-hoc install into the active env
uv venv .venv # create a virtualenv
uv sync # install exactly what the lockfile pins
Use when reviewing a completed implementation holistically - a finished branch, a completed plan step, or a diff before PR. Reviews every changed line against the implementation plan (if one exists) and high engineering standards across seven dimensions, verifies tests by deliberately breaking crucial code, and emits severity-classified findings with a PASS/FAIL verdict.
Use when performing a holistic code review of an implementation - routes to codex:rescue or falls back to a direct subagent, both running the house-style:holistic-review skill
ALWAYS use before any implementation work, review, or planning: designing, writing, editing, refactoring, debugging, reviewing, or generating source code, tests, scripts, config-as-code, or behavior-affecting files. This is a baseline engineering skill and should be invoked even when a more specific language, framework, testing, or database skill also applies.
Use when asked to write, draft, file, or open a GitHub issue - mandates exploring the relevant code to understand the whole problem space, reasoning any proposed solution, and structuring the issue with summary, what/why, references, nuances, open questions, and acceptance criteria. Adds professionalism and no-sensitive-info discipline for public repos.
Use when creating, editing, triaging, or cleaning up GitHub issues - a mechanical pass that verifies the title is accurate and current, labels/assignees/milestone are correct, and the body is valid, well-formed markdown, all via the gh CLI. Does not judge content quality.
Use when the user provides a reference implementation (URL, repo path, branch, file) plus a verb like "use", "copy", "adapt", "port", "model after" - mandates fetching/reading the reference before designing, and lifting the structure rather than reimagining it.