release

Publish GitHub releases with versioning, notes, tags, CI artifacts, and Homebrew formula.

Updated Feb 22, 2026
One-click install
npx skills add https://github.com/marcelocantos/skills --skill release-marcelocantos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/marcelocantos/skills/tree/main/skills/release
Command: npx skills add https://github.com/marcelocantos/skills --skill release-marcelocantos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the complex, error-prone process of preparing and publishing a project release so maintainers don't manually coordinate versioning, release notes, CI artifact uploads, tagging, and Homebrew formula publication across multiple tools and secrets.

Core Features & Use Cases

  • Automated discovery: Runs a discovery pass to collect tags, commits, build system, CI workflows, Homebrew tap status, version macros, and working-tree state.
  • Versioning and notes: Determines the next semantic version, updates version strings when required, and drafts categorized release notes from commits.
  • CI and Homebrew integration: Proposes or generates release CI workflows that build cross-platform artifacts, upload them to the GitHub release, and optionally run homebrew-releaser with required secrets.
  • Gate checks and safety: Verifies working tree cleanliness, stability/stability audits for pre/post-1.0 projects, third-party attribution, and agent guide/readme coverage before tagging.

Quick Start

Run the release skill to discover the repository state, determine the next version, draft release notes, prepare CI/Homebrew steps, and create the 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 GitHub releases with tags, changelogs, and Homebrew formula updates?

You can automate the entire release process by running a discovery pass to collect commits and tags, determining the next semantic version, drafting categorized release notes, and generating CI workflows for artifact uploads and Homebrew formula publishing.

What is the best way to generate release notes from commits for a new GitHub tag?

The best way to generate release notes from commits is to run an automated discovery pass that audits git history, drafts categorized release notes based on commits, and updates version strings before tagging.

Do I need a HOMEBREW_TAP_TOKEN secret to publish Homebrew formula updates through CI?

Yes, you need an optional HOMEBREW_TAP_TOKEN secret for Homebrew tap publishing. It allows the generated CI workflows to run homebrew-releaser and push formula updates automatically.

Can I use this automated release process for pre-1.0 projects and standalone binaries?

Yes, you can use this automated release process for pre-1.0 projects and standalone binaries. It performs stability audits for pre/post-1.0 projects and applies to GitHub repositories that build standalone binaries or packages.

Why does my release workflow require a clean working tree before tagging and publishing?

A clean working tree is required to prevent unintended changes from being included in the release. Gate checks verify working tree cleanliness, stability audits, and third-party attribution before tagging.