release

Automate deterministic software releases with changelog generation, version bumps, and Homebrew checksum updates.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This Skill prevents broken or inconsistent release artifacts by turning the release process into a deterministic, validated workflow that updates versions and packaging only after compiled binaries and install paths are confirmed.

Core Features & Use Cases

  • Validated, deterministic release flow: Compares dev vs main, drafts a Keep-a-Changelog section from commits, and gates the process with a mandatory compiled-binary smoke test before any version bump.
  • Atomic version + checksum updates: Updates Homebrew formula version and sha256 values together only after binaries are built and checksums.txt is available, avoiding stale formula issues.
  • End-to-end verification via Homebrew installation: Uses /test-release to confirm the install and runtime behavior before the release is considered ready for users.
  • Use Case: When you need to ship a patch/minor/major release from dev to main while ensuring binaries, checksums, Homebrew, and install paths all stay consistent.

Quick Start

Ask your system to run the release process with the appropriate bump by saying: "/release minor".

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 Homebrew formula checksum updates?

Automating a GitHub release with Homebrew formula checksum updates involves generating changelog entries, bumping versions, tagging releases, and atomically syncing sha256 values using checksums.txt after binaries are built and smoke-tested.

What is a deterministic release workflow and when do I need it?

A deterministic release workflow turns version bumping and artifact publishing into a validated process that updates packaging only after compiled binaries and install paths are confirmed, preventing broken or inconsistent release artifacts across branches.

How do I cut a minor release from dev to main using GitHub Actions?

To cut a minor release from dev to main, compare the branches to draft a Keep-a-Changelog section from commits, gate the process with a mandatory compiled-binary smoke test, then bump versions, tag, and create a PR to main.

Why does my Homebrew formula have stale sha256 checksums after a version bump?

Homebrew formula stale sha256 checksums occur when version and sha256 values are not updated together atomically; updating them together only after binaries are built and checksums.txt is available avoids this issue.

How do I verify a release end-to-end using Homebrew installation?

To verify a release end-to-end using Homebrew installation, run /test-release to confirm the install path and runtime behavior before considering the release shippable, ensuring binaries and checksums remain consistent.

Can I use this release workflow for both Node and Bun projects?

Yes, this deterministic release workflow applies to patch, minor, and major release cuts from dev to main for Node, Bun, and other supported stacks where versions and artifacts must remain consistent across branches.