release

Automate AXiomEngine component releases with version-bumped PRs and changelogs.

Updated May 13, 2026
One-click install
npx skills add https://github.com/cliffthelin/AXiomEngine --skill release-cliffthelin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/cliffthelin/AXiomEngine/tree/main/archon/.claude/skills/release
Command: npx skills add https://github.com/cliffthelin/AXiomEngine --skill release-cliffthelin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents broken or inconsistent software releases by automating the full release workflow: validating state, generating a correct changelog, bumping versions, tagging, publishing, and updating Homebrew formulas with verified checksums.

Core Features & Use Cases

  • Deterministic release creation: Creates a release PR from dev to main by diffing changes, drafting Keep a Changelog-style entries, and bumping the correct semantic version (patch/minor/major).
  • Binary smoke-test gate: Runs a mandatory compiled-binary preflight to catch bundler/minification or module-init crashes before any user-visible release steps occur.
  • Checksum-correct Homebrew updates: Waits for release workflow binaries, fetches checksums.txt, then updates homebrew/archon.rb with the new version and SHA256 values atomically, followed by syncing the Homebrew tap and running end-to-end install verification.

Quick Start

Ask the AI to run: /release

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate semantic version bumps and changelog generation for GitHub releases?

Automate semantic version bumps and changelog generation by diffing dev-to-main commits, drafting Keep a Changelog-style entries, and creating a version-bumped release PR. This ensures human-readable changelog entries and correct patch, minor, or major version increments.

What is the best way to update a Homebrew formula with correct SHA256 checksums after a GitHub release?

Update a Homebrew formula with correct SHA256 checksums by waiting for release workflow binaries, fetching checksums.txt, and atomically updating the tap formula with new version and SHA256 values, followed by end-to-end install verification.

How does a binary smoke test prevent broken module initialization during software publishing?

A binary smoke test prevents broken module initialization by running a mandatory compiled-binary preflight check, catching bundler, minification, or module-init crashes before any user-visible release steps occur.

Do I need a clean git state on the dev branch to create a release PR?

Yes, you need a clean git state on the dev branch to create a release PR. The release process requires git state validation on dev before diffing changes, drafting changelog entries, and applying semantic version bumps.

Can I sync Homebrew tap formulas automatically as part of my GitHub Actions release workflow?

Yes, you can sync Homebrew tap formulas automatically within your release workflow. The process updates the formula atomically using checksums.txt outputs and runs final end-to-end verification via test-release commands.

Why should I use an automated release workflow instead of manual Git tagging and publishing?

An automated release workflow prevents broken or inconsistent software releases by validating state, generating correct changelogs, enforcing checksum verification, and applying deterministic semantic version bumping logic across all patch, minor, and major releases.