القائمة
Deploy a Python project to the target environment. Runs pytest, builds the wheel, and pushes a deployment tag. Only invoke manually when ready to deploy.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| title | python-deploy |
| name | python-deploy |
| description | Deploy a Python project to the target environment. Runs pytest, builds the wheel, and pushes a deployment tag. Only invoke manually when ready to deploy. |
| disable-model-invocation | true |
| argument-hint | ["environment"] |
| allowed-tools | Bash(python *) Bash(pip *) Bash(git status) Bash(git log *) Bash(git tag *) Bash(git push *) |
!git status --short
!git log --oneline -5
Deploy to: $ARGUMENTS
If $ARGUMENTS is empty, stop immediately. Report: "No environment specified. Invoke as: /python-deploy (e.g., /python-deploy staging or /python-deploy production)."
Check the git status output above. If it shows any lines (modified, untracked, staged, or deleted files), stop here.
Report: "Deploy aborted: there are uncommitted changes. Commit or stash them before deploying to $ARGUMENTS."
A clean working tree shows no output from git status --short. Do not proceed unless the output is empty.
Run:
python -m pytest
If any tests fail, report the failing test names and count, then stop. Do not proceed.
If pytest is not installed, try:
python -m unittest discover
If neither is available, report that no test runner was found and stop. Do not deploy without running tests.
Run:
python -m build
This requires the build package. If it is not installed, run:
pip install build
Then retry python -m build.
If the build fails, report the error output and stop.
On success, confirm the output: the dist/ directory should contain a .whl and a .tar.gz file.
Construct the tag name:
deploy-$ARGUMENTS-<YYYYMMDD>-<HHMMSS>
Use current UTC date and time. Example: deploy-staging-20260513-143207.
Run:
git tag deploy-$ARGUMENTS-<YYYYMMDD>-<HHMMSS>
Run:
git push origin deploy-$ARGUMENTS-<YYYYMMDD>-<HHMMSS>
If the push fails, report the error and stop.
Print a final summary:
Deploy initiated.
Environment: $ARGUMENTS
Tag: deploy-$ARGUMENTS-<YYYYMMDD>-<HHMMSS>
Time: <YYYY-MM-DD HH:MM:SS UTC>
Build artifacts: dist/
Explains code in plain language for someone unfamiliar with the programming language. Use when asked to explain code, walk through logic, describe what a function does, or when the user says "explain this" or "walk me through this".
Summarizes uncommitted git changes in a concise machine-readable format. Use in CI pipelines, scripts, or headless invocations where the output will be piped or captured.
Explains what a skill is and demonstrates that skills are working. Use when testing skills, when asked about skills, or when asked to demonstrate how skills work.
Demonstrates the personal scope for Claude Code skills. Use when testing personal-scoped skills or when the user wants to understand the difference between personal and project skill scopes.
Lists the conventions for this project and demonstrates the project scope for Claude Code skills. Use when asked about project conventions, code style, or as a demonstration of project-scoped skills.
Draft a CHANGELOG.md entry for the current changes in Keep a Changelog format. Use when releasing, tagging a version, or updating CHANGELOG.md.