# release-manager

release-manager coordinates release pipelines using an agent swarm. It synchronizes versions across packages, executes tests, and opens a GitHub pull request.

- command · `type=command` · Claude Code, Codex, GitHub Copilot, Gemini CLI · ★ 850 repo stars
- Author: ruvnet
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/ruvnet/agentic-flow/tree/HEAD/.claude/commands/github/release-manager.md
- Updated: 2026-10-26
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/commands/release-manager

## What it does

The command organizes release steps with `mcp__claude-flow__*` swarms. Agents split coordination and review tasks. They create a dedicated branch with `mcp__github__create_branch`, bump version fields in multiple `package.json` files, and update `CHANGELOG.md`.

Testing runs next. The workflow invokes `Bash` to run build steps and automated test suites. Once checks pass, it opens a pull request targeting `main` with verification results.

Without active GitHub MCP and claude-flow MCP servers, this command fails because it depends on their tool calls for branch creation and agent coordination.

## Requirements
- Works with: GitHub

## Install

### Claude Code (native platform)

**Manually: put the files in place**
- File: `.claude/commands/release-manager.md` — Call it with /release-manager. For all projects use ~/.claude/commands/

### Codex

**Manually: put the files in place**
- File: `~/.codex/prompts/release-manager.md` — Call it with /prompts:release-manager. Codex marks this format deprecated in favour of skills

### GitHub Copilot

**Manually: put the files in place**
- File: `.github/prompts/release-manager.prompt.md`

### Gemini CLI

**Manually: put the files in place**
- File: `.gemini/commands/release-manager.toml` — Gemini stores commands as TOML: the prompt text goes into the prompt field

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/ruvnet/agentic-flow/tree/HEAD/.claude/commands/github/release-manager.md

## When to use it
- synchronize versions across multiple `package.json` files
- create release branches and generate changelog entries
- run build checks and test suites before deployment
- generate a release pull request with validation reports

## Example prompts
- /release-manager prepare v1.0.72 release for the repository
- /release-manager synchronize package versions and run test suites
- /release-manager generate release branch and open final PR

## Similar
- [release](https://affpapa.org/en/nevibecode/skills/ldayton-release.md) — skill · ★ 244 repo stars
- [create-release-checklist](https://affpapa.org/en/nevibecode/skills/create-release-checklist.md) — skill · 779 installs
- [github-release-management](https://affpapa.org/en/nevibecode/skills/github-release-management.md) — skill · 1200 installs
- [release-skills](https://affpapa.org/en/nevibecode/skills/release-skills.md) — skill · 26100 installs
- [Open Source Release Checklist Builder (YAML)](https://affpapa.org/en/nevibecode/prompts/open-source-release-checklist-builder-yaml.md) — prompt · ★ 178201 repo stars
- [re0-release](https://affpapa.org/en/nevibecode/skills/re0-release.md) — skill · 1400 installs

From the same set: [ruvnet/agentic-flow](https://affpapa.org/en/nevibecode/by/ruvnet/agentic-flow.md) — 76 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
