python-uv-workflow
Apply Python development policy using uv-first execution, test-first behavior validation, and pre-commit quality gates. Use when implementing or refactoring Python code.
- License 许可
- MIT
- 所属仓库
- mryfmo/dotfiles
- 最近更新
- 2026-11-12
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- python-uv-workflow
- description
- Apply Python development policy using uv-first execution, test-first behavior validation, and pre-commit quality gates. Use when implementing or refactoring Python code.
02 资源文件 2
- 参考文档agents/openai.yaml275 B
- 参考文档references/python-uv-rules.md1.7 KB
03 SKILL.md 正文
Python UV Workflow
Overview
Use this workflow to keep Python implementation and refactoring aligned with repository policy.
Read Acknowledgement
- After reading this skill, say:
🐍 私は python-uv-workflow を読みました。
Workflow
- Use
uvas the default toolchain for Python projects. - Run scripts with
uv run <script>. - Write tests when behavior changes and verify expected behavior.
- Add standard dev dependencies with
uv. - Install pre-commit hooks after dependency setup.
- Create
.pre-commit-config.yamlwhen missing. - Create
Makefilewithsetuptarget when missing. - For refactoring from non-
uvoriginals, align dependencies, raise coverage, and verify output parity.
Testing Expectations
- Add tests before refactoring.
- Prefer real data over mocks and monkeypatches when feasible.
- Target coverage expansion toward 90%+ for refactoring tasks.
Use python-uv-rules.md for exact commands and canonical hook configuration.
04 同仓库更多 Skills
x
暂无简介
y
暂无简介
status-report
Generate a status report with KPIs, risks, and action items. Use when writing a weekly or monthly update for leadership, summarizing project health with green/yellow/red status, surfacing risks and decisions that need stakeholder attention, or turning a pile of project tracker activity into a readable narrative.
runbook
Create or update an operational runbook for a recurring task or procedure. Use when documenting a task that on-call or ops needs to run repeatably, turning tribal knowledge into exact step-by-step commands, adding troubleshooting and rollback steps to an existing procedure, or writing escalation paths for when things go wrong.
risk-assessment
Identify, assess, and mitigate operational risks. Trigger with "what are the risks", "risk assessment", "risk register", "what could go wrong", or when the user is evaluating risks associated with a project, vendor, process, or decision.
change-request
Create a change management request with impact analysis and rollback plan. Use when proposing a system or process change that needs approval, preparing a change record for CAB review, documenting risk and rollback steps before a deployment, or planning stakeholder communications for a rollout.