deployment-git

Coordinate SDK release onboarding, CI/CD setup, and Git workflows for the Kailash Python SDK.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinates structured, repeatable deployment and release workflows for the Kailash Python SDK, unifying PyPI publishing, CI/CD pipelines, documentation deployment, and GitHub-based release governance.

Core Features & Use Cases

  • Onboarding and runbooks for SDK releases, including versioning, build, test, and publication steps across all packages.
  • CI/CD patterns and templates for GitHub Actions, multi-platform builds, documentation deployment, and multi-package coordination.
  • Git workflow guidance for branching, tagging, release management, and cross-package dependency alignment.
  • Use Case: when preparing a major SDK release, consult this skill to execute the end-to-end process from code changes to PyPI publication and GitHub Release.

Quick Start

Instantiate a release runbook by following onboarding steps and execute the automated CI/CD workflow for a tagged release.

Frequently Asked Questions about deployment-git

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

FAQPage Schema
How do I set up a Git workflow for multi-package Python SDK releases?

A Git workflow for multi-package Python SDK releases coordinates branching, tagging, and cross-package dependency alignment so core and framework packages publish consistently. It applies versioning rules and documented runbooks to orchestrate the end-to-end release process across a monorepo.

What's the best way to automate PyPI publishing with GitHub Actions CI/CD?

Automating PyPI publishing with GitHub Actions CI/CD uses pipeline patterns and templates for multi-platform builds and multi-package coordination. It executes tagged releases through build, test, and publication steps, applying release governance for consistent PyPI deployment.

When do I need a release runbook for Python SDK deployment?

A release runbook for Python SDK deployment is needed when preparing a major release that unifies PyPI publishing, CI/CD pipelines, documentation deployment, and GitHub Release governance. It onboards versioning, build, test, and publication steps across all packages for repeatable execution.

Can I align core and framework package versions during a monorepo release?

Aligning core and framework package versions during a monorepo release follows Git workflow guidance for tagging and cross-package dependency alignment. It enforces versioning rules and documented runbooks to keep all packages consistent across the release cycle.

Does this deployment workflow handle documentation deployment alongside code releases?

This deployment workflow handles documentation deployment alongside code releases by including CI/CD patterns and templates for documentation deployment within the GitHub Actions pipeline. It unifies documentation publishing with PyPI releases and GitHub Release governance.

What are the limitations of coordinating SDK releases across a monorepo?

Coordinating SDK releases across a monorepo requires strict adherence to documented runbooks, versioning rules, and dependency alignment between core and framework packages. Without consistent tagging and CI/CD governance, multi-package releases risk version mismatch and failed deployments.