github-release-management

Automate GitHub release management with semantic versioning, testing, deployment, and rollback.

Updated Sep 16, 2025
One-click install
npx skills add https://github.com/ellisapotheosis/Project-Nyra --skill github-release-management-ellisapotheosis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-release-management
Source: https://github.com/ellisapotheosis/Project-Nyra/tree/main/.claude/skills/github-release-management
Command: npx skills add https://github.com/ellisapotheosis/Project-Nyra --skill github-release-management-ellisapotheosis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, claude-flow, ruv-swarm, git, npm or yarn, node (>= 20.0.0).

What problem does it solve?

This Skill automates and orchestrates the entire GitHub release process, from version planning and changelog generation to multi-platform deployment and rollback management. It eliminates manual errors, ensures consistency, and accelerates release cycles, allowing teams to deploy software faster and more reliably.

Core Features & Use Cases

  • Release Planning & Version Management: Semantic version analysis, breaking change detection, and multi-package coordination.
  • Automated Testing & Validation: Orchestrates multi-stage, cross-platform testing and security scanning.
  • Build & Deployment Orchestration: Manages parallel artifact generation and progressive deployment strategies.
  • Use Case: Orchestrate a full release for a monorepo, where the skill automatically updates versions across multiple packages, generates a consolidated changelog, runs cross-package compatibility tests, and deploys to various targets (npm, Docker, GitHub Releases) with a staged rollout.

Quick Start

Plan and create a draft release for version 2.0.0: gh release create v2.0.0 --draft --generate-notes --title "Release v2.0.0" Then orchestrate with swarm: npx claude-flow github release-create --version "2.0.0" --build-artifacts --deploy-targets "npm,docker,github"

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 GitHub releases with semantic versioning and changelog generation?

Automate GitHub releases by using semantic version analysis to detect breaking changes, then automatically generate changelogs and release notes coordinated across your codebase. This Skill orchestrates the entire process—from version planning through multi-platform deployment—eliminating manual steps and ensuring consistency across releases.

Can I automate release management for a monorepo with multiple packages?

Yes. This Skill coordinates versioning, testing, and deployment across multiple packages in a monorepo. It updates versions consistently, generates a consolidated changelog, runs cross-package compatibility tests, and deploys to multiple targets like npm, Docker, and GitHub Releases in a staged rollout.

What's the best way to orchestrate CI/CD workflows with automated testing and security scanning before deployment?

Orchestrate multi-stage, cross-platform testing and security scanning as part of your release pipeline. This Skill automates validation across your build matrix, runs security checks, manages parallel artifact generation, and implements progressive deployment strategies with built-in rollback capabilities.

Does this work with GitHub CLI and AI swarm orchestration tools?

Yes. This Skill integrates with GitHub CLI (gh), claude-flow, and ruv-swarm for AI-driven release orchestration. It coordinates with mcp-github and leverages Node.js (≥20.0.0) and npm or yarn for build and deployment automation.

How do I implement automated rollback if a deployment fails?

This Skill includes built-in rollback management as part of its release orchestration. It detects deployment failures and automatically triggers rollback procedures, ensuring you can safely revert to a previous stable version without manual intervention.

Can I detect breaking changes automatically during release planning?

Yes. Breaking-change detection is built into the semantic version analysis phase. The Skill identifies incompatible changes in your codebase during release planning, helping you plan version bumps accurately and communicate impact to users through generated release notes.