release-orchestrator

Automate release processes for versioning, changelogs, and multi-environment deployment.

Updated Aug 27, 2026

Search Tags:#git #changelog #ci/cd #versioning #deployment #release

Ready to run

npx skills add https://github.com/benreceveur/claude-workflow-engine --skill release-orchestrator

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release-orchestrator
Source: https://github.com/benreceveur/claude-workflow-engine/tree/main/skills/release-orchestrator
Command: npx skills add https://github.com/benreceveur/claude-workflow-engine --skill release-orchestrator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

End-to-end release automation with semantic versioning, changelogs, and multi-environment deployment.

Core Features & Use Cases

Calculate version
Generate changelog
Build release assets
Create git release
Deploy to environments

Quick Start

Calculate next version and generate release.

Frequently Asked Questions about release-orchestrator

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

FAQPage Schema

How do I automate semantic versioning and changelog generation in my CI/CD pipeline?▼

Semantic versioning automation parses conventional commits to calculate the next version number, then generates changelogs documenting changes across commits. This approach eliminates manual version bumping and keeps release notes synchronized with code changes in CI/CD workflows.

Can I deploy to multiple environments with automated git tagging and release publishing?▼

Multi-environment deployment automates staging and production rollouts by creating git tags, publishing releases to GitHub or GitLab, and orchestrating asset packaging across environments. This centralizes release control and ensures consistent deployment steps.

What's the best way to handle pre-release versions and rollbacks in automated deployments?▼

Pre-release handling manages non-production versions separately, while rollback capability lets you revert deployments if health checks fail or production approvals are rejected. Together they reduce deployment risk and enable recovery without manual intervention.

How do I integrate release automation with GitHub or GitLab workflows?▼

Release automation integrates with GitHub and GitLab by parsing conventional commits, creating release tags, and publishing release artifacts directly to your repository platform. This keeps your deployment pipeline and version history synchronized in one system.

Does release automation work with conventional commits and custom versioning schemes?▼

Release automation parses conventional commits to determine version bumps following semantic versioning rules. It supports standard naming conventions for calculating major, minor, and patch increments automatically from your commit history.