deployment-git

Guides PyPI publishing, CI/CD pipelines, and Git release workflows for Python SDKs.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/Dchuuuuuu/disease-risk-classifier --skill deployment-git-dchuuuuuu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: deployment-git
Source: https://github.com/Dchuuuuuu/disease-risk-classifier/tree/main/.claude/skills/10-deployment-git
Command: npx skills add https://github.com/Dchuuuuuu/disease-risk-classifier --skill deployment-git-dchuuuuuu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Releasing a multi-package Python SDK involves error-prone manual steps: version bumps across packages, TestPyPI validation, wheel building, CI pipeline configuration, and Git tagging. This Skill encodes the full release runbook so releases follow a consistent, verified procedure instead of ad-hoc memory. ## Core Features & Use Cases - PyPI Release Runbook: Step-by-step procedures for version consistency checks, TestPyPI validation, dependency-ordered publishing, and rollback via yanking. - CI/CD Pipeline Patterns: GitHub Actions templates for test matrices, multi-platform wheel builds (including maturin/Rust), tag-triggered publishing with OIDC trusted publishers, and documentation deployment. - Git & GitHub Workflows: Branching strategies, conventional commit formats, PR templates, issue/project board management, and todo-to-GitHub issue synchronization. - Use Case: When preparing to release kailash v0.9.26, invoke this Skill to verify version consistency across all sub-packages, run the pre-release checklist, tag the release, and let CI publish wheels to PyPI in dependency order. ## Quick Start Ask the AI to walk you through releasing version X.Y.Z of your Python package to PyPI using the release runbook.

Frequently Asked Questions about deployment-git

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I publish a Python package to PyPI?▼

Build wheels with python -m build, upload to TestPyPI first with twine upload --repository testpypi dist/*.whl, verify installation in a clean venv, then upload to production PyPI. Use trusted publisher (OIDC) or ~/.pypirc for credentials, never commit tokens to source.

How do I set up GitHub Actions for Python package releases?▼

Create a tag-triggered workflow that builds wheels across your platform matrix, runs tests, publishes to TestPyPI, then production PyPI using pypa/gh-action-pypi-publish with OIDC. Pushing a version tag like v1.2.3 triggers the full pipeline automatically.

How do I coordinate releases for multiple dependent Python packages?▼

Publish in dependency order: core package first, then dependent packages after verifying each is available on PyPI with pip install --dry-run. Ensure version consistency across all pyproject.toml and __init__.py files, and update cross-package dependency pins when bumping versions.

Can I delete a bad release from PyPI?▼

PyPI does not allow deletion; you yank the version through Project Settings instead. Then publish a corrective release with a bumped patch number. For GitHub, delete the release with gh release delete and remove the tag locally and remotely.

Why does my wheel build fail on CI but pass locally?▼

Common causes include missing system dependencies on Linux runners, wrong macOS SDK versions, or environment differences in Python version and OS. Check CI logs with gh run view, verify your test matrix matches local conditions, and add apt-get install steps for system dependencies.