release

Automate software releases with version bumps, changelogs, and GitHub releases.

116|56|Updated Jan 18, 2026
One-click install
npx skills add https://github.com/Soul-Brews-Studio/arra-oracle-skills-cli --skill release-soul-brews-studio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/Soul-Brews-Studio/arra-oracle-skills-cli/tree/main/src/skills/release
Command: npx skills add https://github.com/Soul-Brews-Studio/arra-oracle-skills-cli --skill release-soul-brews-studio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the full release cycle: bump version, generate a changelog, tag the release, push to the remote repository, and create a GitHub release to publish changes.

Core Features & Use Cases

  • Automates version bumps (patch/minor/major) and corresponding git tags.
  • Generates a changelog from commits since the last release and publishes it with the release.
  • Supports dry-run, alpha pre-releases, and optional push control for CI/CD workflows.
  • Ideal for teams practicing semantic versioning and automated release pipelines.

Quick Start

Run /release patch to bump the patch version and publish a GitHub release.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate version bumps and GitHub releases for semantic versioning projects?

Automate version bumps and GitHub releases by running a single command that updates version files, generates a changelog from commits, tags the commit, and publishes via the gh CLI. It enforces preflight checks for consistent, auditable software releases.

Can I test a git release workflow before pushing changes to the remote repository?

Yes, you can test a git release workflow using the --dry-run flag to execute preflight checks and preview version bumps without pushing changes, or use --no-push to commit and tag locally without updating the remote repository.

How is a changelog generated from commits during an automated release?

A changelog is generated automatically by parsing commit history since the last release tag. The extracted commit messages are compiled into a changelog file and published alongside the GitHub release notes.

Does this release automation tool support alpha pre-releases for CI/CD pipelines?

Yes, release automation supports alpha pre-releases through the --alpha flag, enabling CI/CD pipelines to publish pre-release versions while maintaining semantic versioning conventions and automated tag creation.

What prerequisites are needed to publish GitHub releases automatically via CLI?

Publishing GitHub releases automatically requires a git repository using semantic versioning and the gh CLI installed and authenticated. The tool executes preflight checks to verify these dependencies before bumping versions and creating annotated tags.