release-management

Automate GitHub releases with semantic versioning and the gh CLI.

217|20|Updated Dec 31, 2025
One-click install
npx skills add https://github.com/yonatangross/orchestkit --skill release-management-yonatangross
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-management
Source: https://github.com/yonatangross/orchestkit/tree/main/plugins/ork/skills/release-management
Command: npx skills add https://github.com/yonatangross/orchestkit --skill release-management-yonatangross

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the process of creating GitHub releases, ensuring versioning consistency, generating changelogs, and automating release tasks, thereby reducing manual errors and saving development time.

Core Features & Use Cases

  • Automated Release Creation: Create new GitHub releases with version tags and auto-generated notes from pull requests.
  • Semantic Versioning Enforcement: Guides users on adhering to MAJOR.MINOR.PATCH versioning rules.
  • Changelog Generation: Assists in creating comprehensive changelogs that detail changes, including breaking ones.
  • Use Case: When preparing to launch version 2.0.0 of your software, this Skill can help you tag the release, generate release notes summarizing all new features and breaking changes from merged pull requests, and ensure the changelog is accurate.

Quick Start

Use the release-management skill to create a new release for version 1.2.0, automatically generating notes from merged pull requests and uploading the dist/app.zip artifact.

Frequently Asked Questions about release-management

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

FAQPage Schema
How do I automate GitHub releases with semantic versioning?

Automate GitHub releases using semantic versioning by leveraging the gh CLI to manage version bumping, generate changelogs from commit history, and upload release artifacts. This enforces MAJOR.MINOR.PATCH rules and validates version integrity.

Can I generate a changelog automatically from merged pull requests before a release?

Yes, you can generate a changelog automatically from merged pull requests. The release process extracts commit history to summarize new features and breaking changes, ensuring changelog completeness through integrated validation rules before publishing.

Does this release automation tool support hotfix workflows?

Yes, this release automation tool supports both standard and hotfix release workflows. It applies semantic versioning enforcement and changelog validation rules to ensure version integrity across different release paths.

How do I ensure changelog completeness and version integrity during version bumping?

Ensure changelog completeness and version integrity during version bumping through integrated validation rules. The automation checks that the changelog accurately details all changes, including breaking ones, before creating the GitHub release tag.

What is the best way to upload release artifacts to GitHub automatically?

The best way to upload release artifacts to GitHub automatically is by using the gh CLI within the release workflow. It handles version tagging, changelog generation, and artifact uploads like dist/app.zip in a single automated process.

Do I need the gh CLI installed to manage version bumping and GitHub releases?

Yes, you need the gh CLI installed to manage version bumping and GitHub releases. The automation relies on the gh CLI to interact with GitHub, create version tags, and upload artifacts seamlessly.