release

Tag commits with semantic versions and publish release assets via GitHub Releases.

Updated Apr 6, 2026

Search Tags:#git #versioning #release #release-management #github-actions #ci-cd #tagging

Ready to run

npx skills add https://github.com/mistakenot/auto-stack --skill release-mistakenot

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release
Source: https://github.com/mistakenot/auto-stack/tree/main/.agents/skills/release
Command: npx skills add https://github.com/mistakenot/auto-stack --skill release-mistakenot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the process of tagging a commit and publishing a release, reducing manual steps and ensuring consistency in software releases.

Core Features & Use Cases

Release tagging: Tag a commit with a semantic version and trigger release workflows.
Cross-platform publishing: Build and publish release assets for multiple targets (e.g., linux-amd64, darwin-arm64) via GitHub Releases.
Use Case: When preparing a new version, push a vX.Y.Z tag and let CI publish binaries and release notes automatically.

Quick Start

Push a semver tag (for example v0.8.0) to the repository to trigger the release workflow.

Frequently Asked Questions about release

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

FAQPage Schema

How do I automate git release tagging and publishing with GitHub Actions?▼

To automate release tagging and publishing, push a semantic version tag like v0.8.0 to your repository. This triggers a GitHub Actions workflow that automatically builds cross-platform binaries and publishes release assets.

What is the best way to enforce semantic versioning for GitHub Releases?▼

Enforcing semantic versioning is handled by tagging commits with vX.Y.Z prefixes. This ensures consistent version tracking and triggers the release workflow to generate and publish the corresponding release assets.

Can I build and publish cross-platform release assets in one workflow?▼

Yes, you can build and publish cross-platform release assets for targets like linux-amd64 and darwin-arm64. The workflow uses GitHub Releases to automatically distribute these compiled binaries when a valid tag is pushed.

Does release tagging require a specific tag format to trigger GitHub Actions?▼

Yes, release tagging requires a v* prefix tag format to trigger the GitHub Actions workflow. Pushing a properly formatted semantic version tag ensures the CI pipeline recognizes the release and begins asset publishing.

Why does pushing a tag to my repository not trigger the release workflow?▼

If pushing a tag does not trigger the release workflow, ensure the tag strictly follows the semantic versioning format with a v prefix, such as v1.0.0. The automation only activates when this specific tag format is detected.