release

Name: release
Availability: InStock
Author: cerisonautomation

Dispatch a GitHub Actions Release workflow with a patch, minor, or major version bump.

Updated Aug 23, 2026

Search Tags:#publishing #github actions #release #semantic versioning #release automation #version bump #workflow dispatch

Ready to run

npx skills add https://github.com/CerisonAutomation/clud --skill release-cerisonautomation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release
Source: https://github.com/CerisonAutomation/clud/tree/main/.claude/skills/release
Command: npx skills add https://github.com/CerisonAutomation/clud --skill release-cerisonautomation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes the manual, error-prone steps of cutting a new software release by delegating the full bump-and-publish process to a GitHub Actions workflow.

Core Features & Use Cases

Dispatches a Release workflow: Triggers the Release workflow via workflow dispatch with a specified bump type.
Supports controlled versioning: Accepts patch, minor, or major bump types and defaults to patch when none is provided.
Verifies initiation: Lists recent workflow runs to confirm the dispatch started.

Quick Start

Ask the assistant to run the release bump with a patch version using the command: release patch

Frequently Asked Questions about release

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

FAQPage Schema

How do I automate a GitHub release with semantic versioning?▼

Automating a GitHub release involves dispatching a GitHub Actions Release workflow with a specified version bump type. This Skill triggers that workflow using the gh CLI against your main branch to coordinate version bumping, tagging, and publishing across packages.

How do I trigger a GitHub Actions workflow dispatch for a release?▼

Triggering a workflow dispatch for a release requires invoking gh workflow run against the target repository ref main. This Skill automates that invocation while passing a controlled bump field to initiate the coordinated publishing process.

What version bump types are supported for release automation?▼

Release automation supports patch, minor, and major version bump types. When no bump type is explicitly provided, the system validates the input and defaults to a patch version bump to ensure safe incremental releases.

Can I verify if a GitHub Actions release workflow started successfully?▼

Verifying workflow initiation is done by listing recent workflow runs to confirm the dispatch started. This Skill performs that check automatically after dispatching the release workflow to ensure the version bump process is running.

Do I need a pre-configured GitHub Actions workflow to use release automation?▼

Release automation requires an existing GitHub Actions Release workflow configured in your target repository. This Skill dispatches that workflow on the main ref, so the repository must already be set up to handle the bump field and publish packages.

Why use a workflow dispatch instead of manual version bumping for releases?▼

Using a workflow dispatch removes the manual, error-prone steps of cutting a new software release. Delegating the bump-and-publish process to a GitHub Actions workflow ensures coordinated version bumping and tagging across platforms without direct human intervention.