release

Name: release
Availability: InStock
Author: arbiterForge

Derive SemVer from Conventional Commits and publish annotated tags and GitHub Releases.

139|7|Updated May 8, 2026

Search Tags:#git #changelog #conventional commits #github #release #semver

Ready to run

npx skills add https://github.com/arbiterForge/codeArbiter --skill release-arbiterforge

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release
Source: https://github.com/arbiterForge/codeArbiter/tree/main/plugins/ca/skills/release
Command: npx skills add https://github.com/arbiterForge/codeArbiter --skill release-arbiterforge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents unsafe or guesswork-driven releases by forcing versioning, changelog updates, tagging, and publication through a strict, auditable gate sequence.

Core Features & Use Cases

Deterministic Versioning: Derives the next SemVer from Conventional Commits instead of manual judgment.
Release Surface Sync: Keeps the manifest, changelog, badges, and command catalogs aligned before a tag is created.
Controlled Publication: Creates annotated tags locally and publishes GitHub Releases only after explicit authorization and verification.

Quick Start

Use the release skill to derive the next version from the commit history, update the changelog, and prepare the annotated tag for the ca plugin.

Frequently Asked Questions about release

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

FAQPage Schema

How do I automate SemVer derivation from Conventional Commits for GitHub releases?▼

Automating SemVer derivation from Conventional Commits requires parsing your commit history to automatically determine the next version number, preventing manual guesswork and ensuring deterministic versioning for your GitHub releases.

What is the safest way to update a changelog and publish an annotated git tag?▼

The safest way to update a changelog and publish an annotated git tag is using a strict gating sequence that enforces clean trees, synchronizes catalogs, and verifies the published release locally before final publication.

How do I prevent unsafe releases when using branch-based git workflows?▼

Preventing unsafe releases in branch-based git workflows requires enforcing branch safety checks and payload-scoped commit windows, ensuring versioning and tag publication only proceed after explicit authorization and a clean tree verification.

Does release publication require a clean working tree and explicit authorization?▼

Yes, controlled release publication requires a clean working tree and explicit authorization to create annotated tags and publish GitHub Releases, ensuring all release surface artifacts are synchronized and verified before final publication.

Can I sync my manifest, changelog, and command catalogs before creating a version tag?▼

Syncing your manifest, changelog, and command catalogs before creating a version tag ensures all release surfaces are aligned, preventing desynchronized artifacts when deriving SemVer and publishing annotated git tags.

Why does my automated version tagging fail without branch safety checks?▼

Automated version tagging fails without branch safety checks because strict gating prevents unsafe releases by requiring clean trees, payload-scoped commit windows, and catalog synchronization before authorizing annotated tag creation.