github-release-management

Orchestrates GitHub releases with automated versioning, testing, deployment, and rollback workflows.

11|Updated Jan 20, 2026
One-click install
npx skills add https://github.com/ishandutta2007/claude-agent-orchestration --skill github-release-management-ishandutta2007
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-release-management
Source: https://github.com/ishandutta2007/claude-agent-orchestration/tree/main/.claude/skills/github-release-management
Command: npx skills add https://github.com/ishandutta2007/claude-agent-orchestration --skill github-release-management-ishandutta2007

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating a software release involves many error-prone manual steps: bumping versions, generating changelogs, running validation suites, building artifacts for multiple platforms, publishing to registries, and rolling back when deployments fail. This Skill automates that entire pipeline using GitHub CLI and AI swarm coordination. ## Core Features & Use Cases - Automated Release Pipeline: Semantic version suggestion, categorized changelog generation from commits and merged PRs, and draft release creation via the GitHub CLI. - Multi-Stage Validation & Deployment: Pre-release checks (lint, tests, security scans), multi-platform artifact builds, progressive staged rollouts, and automatic rollback on metric thresholds. - Swarm-Orchestrated Coordination: Specialized agents (changelog, version, build, test, deploy) coordinate releases across monorepos and multiple repositories, including emergency hotfix fast-tracking. - Use Case: A team preparing v2.0.0 of an npm package uses the Skill to generate a categorized changelog from merged PRs, run the full validation suite, publish to npm and Docker, and monitor error rates with auto-rollback configured. ## Quick Start Ask the AI to create a draft GitHub release for version 2.0.0 with a generated changelog and full test validation before publishing to npm.

Frequently Asked Questions about github-release-management

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

FAQPage Schema
How do I automate a GitHub release with the GitHub CLI?

Use gh release create with a version tag, the --generate-notes flag for automatic release notes, and --draft to review before publishing. This Skill extends that flow with changelog categorization, validation runs, and multi-target deployment.

How to generate a changelog from merged pull requests?

List merged PRs with gh pr list filtered by merge date, fetch commits via the GitHub compare API, then categorize entries by labels such as feature, bug, and breaking. The Skill's changelog command automates this and can add a migration guide.

Does this release workflow support monorepos with multiple packages?

Yes. It coordinates multi-package releases by spawning per-package agents, aligning dependency versions, running cross-package integration tests, and creating a unified release PR for all updated packages.

Can I set up automatic rollback for a failed deployment?

Yes. Configure auto-rollback triggers such as error rate above 5%, p99 latency above a threshold, or availability below 99%, with a grace period before reverting. Rollbacks preserve data and notify stakeholders.

What tools are required to run this release automation?

The GitHub CLI (gh) and claude-flow are required, along with git, Node.js 20 or later, and npm or yarn. The ruv-swarm and mcp-github integrations are optional for enhanced swarm coordination.

How do I handle an emergency hotfix release?

Create a hotfix branch from the last stable tag, cherry-pick the fix commits, run critical tests only, then publish a patch release. The emergency-release command fast-tracks this flow and notifies stakeholders automatically.