Skip to main content

uv-workflow

Use when a coding agent needs to run Python code, modules, one-liners, tools, tests, or standalone scripts through uv, or create and maintain PEP 723 scripts with uv init/add/remove --script. Avoid direct python/python3 shell entrypoints.

来源信息

仓库
bahayonghang/my-ai-cli-toolkit
最近来源活动
2026年10月6日 14:36
检测到的 SKILL.md 语言
英语
星标
17
Forks
0

安装方式

默认使用会先检查来源的 Prompt;你也可以切换为直接命令,或下载本地副本。

检查来源文件

决定是否安装前,请先阅读 SKILL.md,以及 SkillsMP 当前展示的配套文件。

文件资源管理器
5 个文件

正在显示 SKILL.md

SKILL.md
来源说明 · 只读预览
name
uv-workflow
description
Use when a coding agent needs to run Python code, modules, one-liners, tools, tests, or standalone scripts through uv, or create and maintain PEP 723 scripts with uv init/add/remove --script. Avoid direct python/python3 shell entrypoints.
category
developer-tools-integrations
tags
["uv","python","scripts","dependencies","tooling"]
version
0.1.0
argument-hint
[python-command-or-script-task]
allowed-tools
Read, Write, Edit, Bash
# uv Workflow Use `uv` as the entrypoint for Python execution and standalone script management. ## Core Rules - Do not run `python` or `python3` as the shell entrypoint. - Translate direct Python commands into the closest `uv` form before running them. - `python` inside `uv run ...` is acceptable because `uv` controls interpreter selection and environment setup. - When sandboxed or when cache writes may fail, set `UV_CACHE_DIR` to a writable temporary directory before running `uv`. - For standalone PEP 723 scripts, let `uv` manage inline metadata. Do not hand-edit metadata blocks. ## Command Map | Need | Use | | --- | --- | | Run a script | `uv run path/to/script.py` | | Run a module | `uv run -m package.module` | | Run a one-liner | `uv run python -c "print('hello')"` | | Run a dependency-provided tool | `uv run tool-name` | | Add an ad hoc dependency | `uv run --with package python -c "..."` | | Run tests | `uv run pytest` or `uv run -m pytest` | | Create a standalone script | `uv init --script path/to/script.py` | | Add a script dependency | `uv add --script path/to/script.py package` | | Remove a script dependency | `uv remove --script path/to/script.py package` | ## Standalone Script Workflow For a new single-file script: 1. Initialize it with `uv init --script path/to/script.py`. 2. Add dependencies with `uv add --script path/to/script.py <package>`. 3. Edit the Python code normally. 4. Run it with `uv run path/to/script.py`. 5. Remove dependencies with `uv remove --script path/to/script.py <package>`. Use `uv init --script` even when the script already exists conceptually and only needs to be created on disk. ## Scope Boundary Use this skill for Python execution, Python tools, tests, one-liners, and standalone PEP 723 scripts. If the task is about a full Python project with `pyproject.toml`, use project-oriented `uv` commands instead of script-specific metadata commands. Keep `uv` as the entrypoint, but do not force `uv init --script` or `uv add --script` onto project workflows. ## More Patterns Read `references/uv-command-patterns.md` for PowerShell and POSIX cache setup, script lifecycle examples, and project-vs-script guidance.
在 GitHub 查看