agent-release-manager

Automates multi-package release coordination, testing, and deployment using ruv-swarm orchestration.

70.1k|8.4k|Updated Jun 2, 2025
One-click install
npx skills add https://github.com/ruvnet/claude-flow --skill agent-release-manager
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-release-manager
Source: https://github.com/ruvnet/claude-flow/tree/main/.agents/skills/agent-release-manager
Command: npx skills add https://github.com/ruvnet/claude-flow --skill agent-release-manager

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating releases across multiple packages requires manual version bumps, changelog updates, test runs, and pull request creation, which is error-prone and slow. This Skill orchestrates the entire release pipeline with swarm agents so versioning, validation, and deployment happen in a coordinated, repeatable workflow.

Core Features & Use Cases

  • Automated Release Pipelines: Initializes a swarm of coordinator, tester, reviewer, and analyst agents to prepare and validate releases end to end.
  • Multi-Package Version Coordination: Updates package.json versions, changelogs, and release notes across repositories like claude-flow and ruv-swarm in a single commit.
  • Validation and PR Creation: Runs install, test, lint, and build steps, then opens a release pull request via GitHub MCP tools or the gh CLI with detailed release notes.
  • Use Case: Prepare release v1.0.72 by spawning a release swarm, bumping versions in two packages, running the full test suite, and opening a validated release PR ready for review and merge.

Quick Start

Ask the agent to prepare release v1.0.72 across claude-flow and ruv-swarm with full testing and a release pull request.

Frequently Asked Questions about agent-release-manager

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

FAQPage Schema
How do I automate a multi-package release with swarm agents?

Initialize a swarm with mcp__claude-flow__swarm_init, spawn coordinator, tester, reviewer, and coder agents, then orchestrate the release task with task_orchestrate. The agents handle version bumps, testing, and pull request creation in sequence.

How to create a release pull request using GitHub MCP tools?

Use mcp__github__create_branch to cut a release branch, mcp__github__push_files to commit updated package.json and CHANGELOG files, then mcp__github__create_pull_request with the release notes as the body. The gh CLI works as an alternative.

Does this release workflow support rollback if deployment fails?

Yes, the skill defines a rollback strategy triggered by test failures, deployment issues, or critical bugs. Automatic rollback covers failed tests and build failures, while manual rollback handles user-reported issues by restoring the previous stable version.

What validation stages run before a release is approved?

The pipeline runs unit tests, integration tests, performance tests, compatibility checks, documentation verification, and deployment simulation. Each package is installed, tested, linted, and built before the release PR is created.

Can I use this with GitHub Actions CI/CD pipelines?

Yes, the skill includes a GitHub Actions workflow example that triggers on pull requests touching package.json or CHANGELOG.md. It sets up Node.js 20, installs dependencies, runs tests for both packages, and validates the release.