github-release-management

Automates GitHub release orchestration including versioning, testing, deployment, and rollback management.

1|1|Updated Nov 28, 2025
One-click install
npx skills add https://github.com/33may/robotics --skill github-release-management-33may
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-release-management
Source: https://github.com/33may/robotics/tree/main/humanoid/.claude/skills/github-release-management
Command: npx skills add https://github.com/33may/robotics --skill github-release-management-33may

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating software releases manually involves error-prone steps like version bumping, changelog writing, multi-platform builds, and staged deployments, which this Skill automates through GitHub CLI commands and AI swarm coordination. ## Core Features & Use Cases - Release Planning & Versioning: Analyzes commits and PRs to suggest semantic versions, detect breaking changes, and generate categorized changelogs with migration guides. - Build, Test & Deploy Orchestration: Coordinates multi-platform builds, validation suites, progressive staged rollouts, and automated rollback on failure. - Multi-Repo & Hotfix Workflows: Synchronizes releases across monorepos or multiple repositories and fast-tracks emergency hotfixes with critical-only testing. - Use Case: A team releasing v2.0.0 uses the Skill to generate a changelog from merged PRs, run validation suites, publish to npm and Docker, and monitor post-release metrics with auto-rollback triggers. ## Quick Start Ask the AI to create a GitHub release for version 2.0.0 with a generated changelog, full test validation, and deployment to npm and Docker.

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 changelog generation?▼

Use gh release create with the --generate-notes flag, or generate a categorized changelog from merged PRs and commits using the claude-flow changelog command. The Skill compares the previous tag to HEAD and categorizes changes by labels like feature, bug, and breaking.

How to coordinate releases across multiple repositories?▼

Use the multi-release command with repository-version pairs like frontend:v2.0.0 and backend:v2.1.0. It ensures cross-repo compatibility, performs atomic synchronized releases, and rolls back all repositories if any single release fails.

Does this release workflow support staged or canary deployments?▼

Yes, the progressive deployment strategy supports canary stages starting at 5% traffic with metric-based auto-advancement. Stages validate error rates and latency before progressing to full rollout, with approval gates and rollback enabled.

How do I handle an emergency hotfix release?▼

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

What triggers an automatic rollback after deployment?▼

Auto-rollback triggers when error rates exceed 5%, p99 latency exceeds configured thresholds, or availability drops below 99%. A grace period of about 5 minutes applies before rollback executes, with notifications sent to configured channels.