cut-release

Automate tag-driven releases for file-search-on across GitHub, ghcr.io, and Homebrew.

5|1|Updated May 3, 2026

Search Tags:#version control #CI/CD #rollback #release automation #software release

Ready to run

npx skills add https://github.com/richardwooding/file-search-on --skill cut-release-richardwooding

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cut-release
Source: https://github.com/richardwooding/file-search-on/tree/main/.claude/skills/cut-release
Command: npx skills add https://github.com/richardwooding/file-search-on --skill cut-release-richardwooding

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, github-actions, goreleaser, homebrew, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the release process for the file-search-on application, handling tag-driven releases, verification of three publish targets, and rollback procedures if needed.

Core Features & Use Cases

Automated Release Workflow: Manages the release process from tag creation to verification of publish targets.
Publish Targets Verification: Checks GitHub Release archives, ghcr.io OCI image, and Homebrew tap commit.
Rollback Procedure: Provides a rollback process in case of failed releases.
Use Case: When a user requests to release a new version of file-search-on, this skill handles the entire process, ensuring that all targets are correctly published.

Quick Start

Run the 'cut-release' skill to initiate the release process for file-search-on.

Frequently Asked Questions about cut-release

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

FAQPage Schema

How do I automate release workflows for Go applications with Homebrew and GitHub Actions?▼

Automating release workflows for Go applications involves managing tag creation, publishing GitHub Release archives, ghcr.io OCI images, and Homebrew tap commits. This skill handles that entire process and verifies all targets.

What is the best way to verify release publish targets across GitHub Releases, ghcr.io, and Homebrew?▼

Verifying release publish targets means checking GitHub Release archives, ghcr.io OCI images, and Homebrew tap commits after deployment. This automated workflow performs these checks to ensure all targets are correctly published.

Do I need GoReleaser and Git to automate tag-driven software releases?▼

Yes, you need GoReleaser and Git, along with GitHub Actions and Homebrew, to automate tag-driven software releases. These tools are required dependencies for creating tags, building artifacts, and publishing to package managers.

Can I rollback a failed release if the GitHub Release or OCI image publishing step breaks?▼

Yes, you can rollback a failed release. If publishing to GitHub Releases, ghcr.io OCI, or Homebrew tap fails, this workflow provides a rollback procedure to revert the release state and resolve errors.

How does a tag-driven release workflow handle OCI image and Homebrew tap publishing?▼

A tag-driven release workflow triggers automated pipelines upon Git tag creation, using GoReleaser to build binaries, push OCI images to ghcr.io, and commit formula updates to a Homebrew tap repository.

When do I need to run a rollback procedure during CI/CD release automation?▼

You need to run a rollback procedure during CI/CD release automation when verification of GitHub Release archives, ghcr.io OCI images, or Homebrew tap commits fails, ensuring your deployment targets remain consistent.