release

Name: release
Availability: InStock
Author: ever-oli

Automate cmux release preparation from version bump to artifact verification.

Updated Aug 23, 2026

Search Tags:#changelog #versioning #release #ci-cd #tagging #pull-request

Ready to run

npx skills add https://github.com/ever-oli/omni-ecosystem --skill release-ever-oli

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release
Source: https://github.com/ever-oli/omni-ecosystem/tree/main/omni-desktop/skills/release
Command: npx skills add https://github.com/ever-oli/omni-ecosystem --skill release-ever-oli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end cmux release workflow, handling version determination, changelog preparation, branch creation, PR management, merging, tagging, and artifact verification to ship releases reliably.

Core Features & Use Cases

Determine the next version, collect user-facing changes, and update CHANGELOG.md.
Open, monitor, and merge a release PR, tag the release, and ensure CI checks pass.
Verify artifacts are published and synchronized with main after release to prevent drift.

Quick Start

Run the release workflow to prepare and publish the next cmux release.

Frequently Asked Questions about release

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

FAQPage Schema

How do I automate changelog drafting and version bumps for a release?▼

Automating changelog drafting and version bumps involves determining the next version, collecting user-facing changes, and updating CHANGELOG.md. This process applies across feature, fix, or hotfix cycles to prepare releases reliably.

What is the best way to manage release PRs and tagging in a CI-CD workflow?▼

Managing release PRs and tagging in a CI-CD workflow requires opening, monitoring, and merging the PR, then creating a tag. This ensures CI checks pass before finalizing the release.

How does artifact verification prevent drift after a release?▼

Artifact verification prevents drift by confirming published artifacts are synchronized with the main branch after the release. This step ensures the repository and deployed artifacts remain consistent.

Can I use this automated release workflow for hotfix cycles?▼

Yes, the automated release workflow supports hotfix cycles alongside feature and fix cycles. It handles branch creation, PR management, and artifact publishing for all these release types.

Do I need to manually update CHANGELOG.md before opening a release PR?▼

No, you do not need to manually update CHANGELOG.md. The workflow collects user-facing changes and automatically drafts the changelog updates before opening the release PR.