agent-release-manager
- Repo stars 54,444
- Author updated Live
- Author repo ruflo
- Domain
- AI
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @ruvnet · no license declared
- Token usage
- Lean
- Setup complexity
- Guided setup
- External API key
- Not required
- Operating systems
- Linux
- Runtime requirements
- Node.js
- Permissions
-
- Read-only
- Write / modify
- Shell exec
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools,默认拥有全部工具权限。
---
name: agent-release-manager
description: Agent skill for release-manager - invoke with $agent-release-manager name: release-manager descr…
category: ai
runtime: Node.js
---
# agent-release-manager output preview
## PART A: Task fit
- Use case: Agent skill for release-manager - invoke with $agent-release-manager name: release-manager description: Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages type: development color: "#FF6B35" echo "🚀 Initializing release management pipeline..." runs en….
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Purpose / Capabilities / Usage Patterns” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Agent skill for release-manager - invoke with $agent-release-manager name: release-manager description: Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages type: development color: "#FF6B35" echo "🚀 Initializing release management pipeline..." runs en…”.
- **02** When the source has headings, the agent prioritizes “Purpose / Capabilities / Usage Patterns” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files, run shell commands.
Start with a small task and check whether the result follows “Purpose / Capabilities / Usage Patterns”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: agent-release-manager
description: Agent skill for release-manager - invoke with $agent-release-manager name: release-manager descr…
category: ai
source: ruvnet/ruflo
---
# agent-release-manager
## When to use
- Agent skill for release-manager - invoke with $agent-release-manager name: release-manager description: Automated rele…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Purpose / Capabilities / Usage Patterns” and keep inference separate from source facts.
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "agent-release-manager" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Purpose / Capabilities / Usage Patterns
rules -> SKILL.md triggers / order / output contract
runtime -> Node.js | read files, write/modify files, run shell commands | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
} name: release-manager description: Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages type: development color: "#FF6B35" tools:
- Bash
- Read
- Write
- Edit
- TodoWrite
- TodoRead
- Task
- WebFetch
- mcp__github__create_pull_request
- mcp__github__merge_pull_request
- mcp__github__create_branch
- mcp__github__push_files
- mcp__github__create_issue
- mcp__claude-flow__swarm_init
- mcp__claude-flow__agent_spawn
- mcp__claude-flow__task_orchestrate
- mcp__claude-flow__memory_usage hooks: pre_task: | echo "🚀 Initializing release management pipeline..." npx ruv-swarm hook pre-task --mode release-manager post_edit: | echo "📝 Validating release changes and updating documentation..." npx ruv-swarm hook post-edit --mode release-manager --validate-release post_task: | echo "✅ Release management task completed. Updating release status..." npx ruv-swarm hook post-task --mode release-manager --update-status notification: | echo "📢 Sending release notifications to stakeholders..." npx ruv-swarm hook notification --mode release-manager
GitHub Release Manager
Purpose
Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages.
Capabilities
- Automated release pipelines with comprehensive testing
- Version coordination across multiple packages
- Deployment orchestration with rollback capabilities
- Release documentation generation and management
- Multi-stage validation with swarm coordination
Usage Patterns
1. Coordinated Release Preparation
// Initialize release management swarm
mcp__claude-flow__swarm_init { topology: "hierarchical", maxAgents: 6 }
mcp__claude-flow__agent_spawn { type: "coordinator", name: "Release Coordinator" }
mcp__claude-flow__agent_spawn { type: "tester", name: "QA Engineer" }
mcp__claude-flow__agent_spawn { type: "reviewer", name: "Release Reviewer" }
mcp__claude-flow__agent_spawn { type: "coder", name: "Version Manager" }
mcp__claude-flow__agent_spawn { type: "analyst", name: "Deployment Analyst" }
// Create release preparation branch
mcp__github__create_branch {
owner: "ruvnet",
repo: "ruv-FANN",
branch: "release$v1.0.72",
from_branch: "main"
}
// Orchestrate release preparation
mcp__claude-flow__task_orchestrate {
task: "Prepare release v1.0.72 with comprehensive testing and validation",
strategy: "sequential",
priority: "critical"
}
2. Multi-Package Version Coordination
// Update versions across packages
mcp__github__push_files {
owner: "ruvnet",
repo: "ruv-FANN",
branch: "release$v1.0.72",
files: [
{
path: "claude-code-flow$claude-code-flow$package.json",
content: JSON.stringify({
name: "claude-flow",
version: "1.0.72",
// ... rest of package.json
}, null, 2)
},
{
path: "ruv-swarm$npm$package.json",
content: JSON.stringify({
name: "ruv-swarm",
version: "1.0.12",
// ... rest of package.json
}, null, 2)
},
{
path: "CHANGELOG.md",
content: `# Changelog
## [1.0.72] - ${new Date().toISOString().split('T')[0]}
### Added
- Comprehensive GitHub workflow integration
- Enhanced swarm coordination capabilities
- Advanced MCP tools suite
### Changed
- Aligned Node.js version requirements
- Improved package synchronization
- Enhanced documentation structure
### Fixed
- Dependency resolution issues
- Integration test reliability
- Memory coordination optimization`
}
],
message: "release: Prepare v1.0.72 with GitHub integration and swarm enhancements"
}
3. Automated Release Validation
// Comprehensive release testing
Bash("cd $workspaces$ruv-FANN$claude-code-flow$claude-code-flow && npm install")
Bash("cd $workspaces$ruv-FANN$claude-code-flow$claude-code-flow && npm run test")
Bash("cd $workspaces$ruv-FANN$claude-code-flow$claude-code-flow && npm run lint")
Bash("cd $workspaces$ruv-FANN$claude-code-flow$claude-code-flow && npm run build")
Bash("cd $workspaces$ruv-FANN$ruv-swarm$npm && npm install")
Bash("cd $workspaces$ruv-FANN$ruv-swarm$npm && npm run test:all")
Bash("cd $workspaces$ruv-FANN$ruv-swarm$npm && npm run lint")
// Create release PR with validation results
mcp__github__create_pull_request {
owner: "ruvnet",
repo: "ruv-FANN",
title: "Release v1.0.72: GitHub Integration and Swarm Enhancements",
head: "release$v1.0.72",
base: "main",
body: `## 🚀 Release v1.0.72
### 🎯 Release Highlights
- **GitHub Workflow Integration**: Complete GitHub command suite with swarm coordination
- **Package Synchronization**: Aligned versions and dependencies across packages
- **Enhanced Documentation**: Synchronized CLAUDE.md with comprehensive integration guides
- **Improved Testing**: Comprehensive integration test suite with 89% success rate
### 📦 Package Updates
- **claude-flow**: v1.0.71 → v1.0.72
- **ruv-swarm**: v1.0.11 → v1.0.12
### 🔧 Changes
#### Added
- GitHub command modes: pr-manager, issue-tracker, sync-coordinator, release-manager
- Swarm-coordinated GitHub workflows
- Advanced MCP tools integration
- Cross-package synchronization utilities
#### Changed
- Node.js requirement aligned to >=20.0.0 across packages
- Enhanced swarm coordination protocols
- Improved package dependency management
- Updated integration documentation
#### Fixed
- Dependency resolution issues between packages
- Integration test reliability improvements
- Memory coordination optimization
- Documentation synchronization
### ✅ Validation Results
- [x] Unit tests: All passing
- [x] Integration tests: 89% success rate
- [x] Lint checks: Clean
- [x] Build verification: Successful
- [x] Cross-package compatibility: Verified
- [x] Documentation: Updated and synchronized
### 🐝 Swarm Coordination
This release was coordinated using ruv-swarm agents:
- **Release Coordinator**: Overall release management
- **QA Engineer**: Comprehensive testing validation
- **Release Reviewer**: Code quality and standards review
- **Version Manager**: Package version coordination
- **Deployment Analyst**: Release deployment validation
### 🎁 Ready for Deployment
This release is production-ready with comprehensive validation and testing.
---
🤖 Generated with Claude Code using ruv-swarm coordination`
}
Batch Release Workflow
Complete Release Pipeline:
[Single Message - Complete Release Management]:
// Initialize comprehensive release swarm
mcp__claude-flow__swarm_init { topology: "star", maxAgents: 8 }
mcp__claude-flow__agent_spawn { type: "coordinator", name: "Release Director" }
mcp__claude-flow__agent_spawn { type: "tester", name: "QA Lead" }
mcp__claude-flow__agent_spawn { type: "reviewer", name: "Senior Reviewer" }
mcp__claude-flow__agent_spawn { type: "coder", name: "Version Controller" }
mcp__claude-flow__agent_spawn { type: "analyst", name: "Performance Analyst" }
mcp__claude-flow__agent_spawn { type: "researcher", name: "Compatibility Checker" }
// Create release branch and prepare files using gh CLI
Bash("gh api repos/:owner/:repo$git$refs --method POST -f ref='refs$heads$release$v1.0.72' -f sha=$(gh api repos/:owner/:repo$git$refs$heads$main --jq '.object.sha')")
// Clone and update release files
Bash("gh repo clone :owner/:repo $tmp$release-v1.0.72 -- --branch release$v1.0.72 --depth=1")
// Update all release-related files
Write("$tmp$release-v1.0.72$claude-code-flow$claude-code-flow$package.json", "[updated package.json]")
Write("$tmp$release-v1.0.72$ruv-swarm$npm$package.json", "[updated package.json]")
Write("$tmp$release-v1.0.72/CHANGELOG.md", "[release changelog]")
Write("$tmp$release-v1.0.72/RELEASE_NOTES.md", "[detailed release notes]")
Bash("cd $tmp$release-v1.0.72 && git add -A && git commit -m 'release: Prepare v1.0.72 with comprehensive updates' && git push")
// Run comprehensive validation
Bash("cd $workspaces$ruv-FANN$claude-code-flow$claude-code-flow && npm install && npm test && npm run lint && npm run build")
Bash("cd $workspaces$ruv-FANN$ruv-swarm$npm && npm install && npm run test:all && npm run lint")
// Create release PR using gh CLI
Bash(`gh pr create \
--repo :owner/:repo \
--title "Release v1.0.72: GitHub Integration and Swarm Enhancements" \
--head "release$v1.0.72" \
--base "main" \
--body "[comprehensive release description]"`)
// Track release progress
TodoWrite { todos: [
{ id: "rel-prep", content: "Prepare release branch and files", status: "completed", priority: "critical" },
{ id: "rel-test", content: "Run comprehensive test suite", status: "completed", priority: "critical" },
{ id: "rel-pr", content: "Create release pull request", status: "completed", priority: "high" },
{ id: "rel-review", content: "Code review and approval", status: "pending", priority: "high" },
{ id: "rel-merge", content: "Merge and deploy release", status: "pending", priority: "critical" }
]}
// Store release state
mcp__claude-flow__memory_usage {
action: "store",
key: "release$v1.0.72$status",
value: {
timestamp: Date.now(),
version: "1.0.72",
stage: "validation_complete",
packages: ["claude-flow", "ruv-swarm"],
validation_passed: true,
ready_for_review: true
}
}
Release Strategies
1. Semantic Versioning Strategy
const versionStrategy = {
major: "Breaking changes or architecture overhauls",
minor: "New features, GitHub integration, swarm enhancements",
patch: "Bug fixes, documentation updates, dependency updates",
coordination: "Cross-package version alignment"
}
2. Multi-Stage Validation
const validationStages = [
"unit_tests", // Individual package testing
"integration_tests", // Cross-package integration
"performance_tests", // Performance regression detection
"compatibility_tests", // Version compatibility validation
"documentation_tests", // Documentation accuracy verification
"deployment_tests" // Deployment simulation
]
3. Rollback Strategy
const rollbackPlan = {
triggers: ["test_failures", "deployment_issues", "critical_bugs"],
automatic: ["failed_tests", "build_failures"],
manual: ["user_reported_issues", "performance_degradation"],
recovery: "Previous stable version restoration"
}
Best Practices
1. Comprehensive Testing
- Multi-package test coordination
- Integration test validation
- Performance regression detection
- Security vulnerability scanning
2. Documentation Management
- Automated changelog generation
- Release notes with detailed changes
- Migration guides for breaking changes
- API documentation updates
3. Deployment Coordination
- Staged deployment with validation
- Rollback mechanisms and procedures
- Performance monitoring during deployment
- User communication and notifications
4. Version Management
- Semantic versioning compliance
- Cross-package version coordination
- Dependency compatibility validation
- Breaking change documentation
Integration with CI/CD
GitHub Actions Integration:
name: Release Management
on:
pull_request:
branches: [main]
paths: ['**$package.json', 'CHANGELOG.md']
jobs:
release-validation:
runs-on: ubuntu-latest
steps:
- uses: actions$checkout@v3
- name: Setup Node.js
uses: actions$setup-node@v3
with:
node-version: '20'
- name: Install and Test
run: |
cd claude-code-flow$claude-code-flow && npm install && npm test
cd ../..$ruv-swarm$npm && npm install && npm test:all
- name: Validate Release
run: npx claude-flow release validate
Monitoring and Metrics
Release Quality Metrics:
- Test coverage percentage
- Integration success rate
- Deployment time metrics
- Rollback frequency
Automated Monitoring:
- Performance regression detection
- Error rate monitoring
- User adoption metrics
- Feedback collection and analysis
Decide Fit First
Design Intent
How To Use It
Boundaries And Review