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/Hamza-Haadi/disease-risk-classifier-hamza --skill deployment-git-hamza-haadi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: deployment-git
Source: https://github.com/Hamza-Haadi/disease-risk-classifier-hamza/tree/main/.claude/skills/10-deployment-git
Command: npx skills add https://github.com/Hamza-Haadi/disease-risk-classifier-hamza --skill deployment-git-hamza-haadi

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, CI pipeline configuration, and Git tagging. This Skill encodes the complete release runbook so nothing is skipped and releases happen in correct dependency order. ## Core Features & Use Cases - PyPI Release Runbook: Step-by-step procedures for version consistency checks, wheel building, TestPyPI validation, production 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 & Project Management Workflows: Branching strategies, conventional commits, PR workflows, GitHub issue templates, and todo-to-GitHub synchronization rules. - Use Case: When releasing kailash v0.9.26, follow the runbook to bump versions in all four packages, push a tag, and let CI build wheels, publish to TestPyPI then PyPI, and create the GitHub Release automatically. ## Quick Start Ask the assistant to walk you through releasing a new version of your Python package to PyPI using the deployment-git skill.

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 with GitHub Actions?▼

Push a version tag to trigger a CI workflow that builds wheels, runs tests, publishes to TestPyPI, then production PyPI using the pypa/gh-action-pypi-publish action with OIDC trusted publisher authentication. No API tokens need to be stored as secrets.

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

Publish in dependency order: core package first, then dependent packages after verifying each is installable from PyPI. Update cross-package dependency pins (e.g., kailash>=X.Y.Z) whenever the core version bumps, and verify version consistency across all pyproject.toml and __init__.py files before releasing.

Should I use TestPyPI before publishing to production PyPI?▼

TestPyPI validation is required for major and minor releases. Upload wheels with twine upload --repository testpypi, then verify installation in a clean virtual environment before publishing to production PyPI.

How do I roll back a bad PyPI release?▼

PyPI does not allow deletion, so yank the version from Project Settings, 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.

What Git branching strategy works for SDK development?▼

Use main for production, develop for integration, and feature/*, release/*, and hotfix/* branches for work in progress. Never commit directly to main, use pull requests for review, and tag releases semantically with conventional commit messages.