
Github Release Management
Orchestrate GitHub releases with gh CLI and optional Claude Flow swarms for versioning, notes, multi-target artifacts, and rollback-aware deployment prep.
Overview
GitHub Release Management is an agent skill most often used in Ship (also Operate infra, Grow lifecycle) that automates GitHub release planning, artifact builds, multi-target deployment orchestration, and rollback-aware
Install
npx skills add https://github.com/ruvnet/ruflo --skill github-release-managementWhat is this skill?
- Simple path: `gh release create` with draft, generated notes, and titled semver tags
- Swarm orchestration via `claude-flow github release-create` with build-artifacts and multi deploy-targets
- Full pipeline mode: hierarchical swarm init plus SPARC pipeline for validated v2.0.0-style releases
- Version 2.0.0 skill documents planning, testing, deployment, and rollback management themes
- Optional MCP GitHub and ruv-swarm coordination; requires Node >= 20 and gh
- Skill version 2.0.0
- Node >= 20.0.0 required
- Example deploy targets: npm, docker, github
Adoption & trust: 644 installs on skills.sh; 58.5k GitHub stars; 1/3 security scanners passed (skills.sh audits).
What problem does it solve?
You are ready to tag a version but manual release steps, changelog drift, and multi-target publishes eat a solo builder's ship window.
Who is it for?
Indie maintainers on Node 20+ with gh installed who want agent-guided release-create and Claude Flow orchestration instead of fragile copy-paste release runbooks.
Skip if: Repos without GitHub, teams forbidding swarm or shell automation on release day, or pure mobile store submission flows with no GitHub release surface.
When should I use this skill?
You are cutting a semver GitHub release and want gh and/or claude-flow swarm orchestration with artifacts and multi-platform deploy targets.
What do I get? / Deliverables
You get a drafted or published GitHub release with generated notes and an optional swarm-driven pipeline that builds artifacts and targets npm, Docker, or GitHub with rollback management hooks.
- GitHub release (draft or published)
- Generated release notes
- Built artifacts for declared deploy targets
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Release management is the Ship phase gate where tagged versions meet production—canonical shelf is launch prep inside Ship. Launch subphase covers release creation, notes, and deploy targets rather than day-two error triage or pure code review.
Where it fits
Cut v2.0.0 as a draft release with generated notes before flipping to latest.
Run a full SPARC pipeline release so validation gates complete before artifacts publish.
Coordinate rollback management after a bad deploy target push from a prior release swarm run.
How it compares
Skill-orchestrated release workflow complementing raw gh CLI—not a substitute for your own CI secrets policy or store-specific ASO launch checklists.
Common Questions / FAQ
Who is github-release-management for?
Solo and small-team maintainers using GitHub CLI and Claude Flow who need semver releases, generated notes, artifacts, and optional AI swarm coordination.
When should I use github-release-management?
At Ship launch when tagging and publishing; in Operate when rolling back or redeploying; after Build when npm/docker/GitHub targets must ship together—when you run `gh release create` or `claude-flow github release-create`.
Is github-release-management safe to install?
It invokes gh, git, npm, and network deploy paths; review the Security Audits panel on this page, scope tokens minimally, and dry-run draft releases before publishing.
Workflow Chain
Then invoke: github pr management, github workflow automation
SKILL.md
READMESKILL.md - Github Release Management
# GitHub Release Management Skill Intelligent release automation and orchestration using AI swarms for comprehensive software releases - from changelog generation to multi-platform deployment with rollback capabilities. ## Quick Start ### Simple Release Flow ```bash # Plan and create a release gh release create v2.0.0 \ --draft \ --generate-notes \ --title "Release v2.0.0" # Orchestrate with swarm npx claude-flow github release-create \ --version "2.0.0" \ --build-artifacts \ --deploy-targets "npm,docker,github" ``` ### Full Automated Release ```bash # Initialize release swarm npx claude-flow swarm init --topology hierarchical # Execute complete release pipeline npx claude-flow sparc pipeline "Release v2.0.0 with full validation" ``` --- ## Core Capabilities ### 1. Release Planning & Version Management - Semantic version analysis and suggestion - Breaking change detection from commits - Release timeline generation - Multi-package version coordination ### 2. Automated Testing & Validation - Multi-stage test orchestration - Cross-platform compatibility testing - Performance regression detection - Security vulnerability scanning ### 3. Build & Deployment Orchestration - Multi-platform build coordination - Parallel artifact generation - Progressive deployment strategies - Automated rollback mechanisms ### 4. Documentation & Communication - Automated changelog generation - Release notes with categorization - Migration guide creation - Stakeholder notification --- ## Progressive Disclosure: Level 1 - Basic Usage ### Essential Release Commands #### Create Release Draft ```bash # Get last release tag LAST_TAG=$(gh release list --limit 1 --json tagName -q '.[0].tagName') # Generate changelog from commits CHANGELOG=$(gh api repos/:owner/:repo$compare/${LAST_TAG}...HEAD \ --jq '.commits[].commit.message') # Create draft release gh release create v2.0.0 \ --draft \ --title "Release v2.0.0" \ --notes "$CHANGELOG" \ --target main ``` #### Basic Version Bump ```bash # Update package.json version npm version patch # or minor, major # Push version tag git push --follow-tags ``` #### Simple Deployment ```bash # Build and publish npm package npm run build npm publish # Create GitHub release gh release create $(npm pkg get version) \ --generate-notes ``` ### Quick Integration Example ```javascript // Simple release preparation in Claude Code [Single Message]: // Update version files Edit("package.json", { old: '"version": "1.0.0"', new: '"version": "2.0.0"' }) // Generate changelog Bash("gh api repos/:owner/:repo$compare$v1.0.0...HEAD --jq '.commits[].commit.message' > CHANGELOG.md") // Create release branch Bash("git checkout -b release$v2.0.0") Bash("git add -A && git commit -m 'release: Prepare v2.0.0'") // Create PR Bash("gh pr create --title 'Release v2.0.0' --body 'Automated release preparation'") ``` --- ## Progressive Disclosure: Level 2 - Swarm Coordination ### AI Swarm Release Orchestration #### Initialize Release Swarm ```javascript // Set up coordinated release team [Single Message - Swarm Initialization]: mcp__claude-flow__swarm_init { topology: "hierarchical", maxAgents: 6, strategy: "balanced" } // Spawn specialized agents mcp__claude-flow__agent_spawn { type: "coordinator", name: "Release Dir