Tag-based releases

Automates GitHub releases for tags matching v* via a workflow file.

147|5|Updated Jan 11, 2026

Search Tags:#automation #workflow #github #notes #releases #tagging #autorelease

Ready to run

npx skills add https://github.com/rcarmo/agentbox --skill tag-based-releases

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Tag-based releases
Source: https://github.com/rcarmo/agentbox/tree/main/skel/.github/skills/release
Command: npx skills add https://github.com/rcarmo/agentbox --skill tag-based-releases

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually creating GitHub releases for every tag is tedious and error-prone; this skill automates the process and ensures consistent release notes.

Core Features & Use Cases

Auto-create releases for tags that match a version pattern (e.g., v1.2.3).
Generate release notes automatically from commit messages and PR data.
Publish the release via a GitHub Actions workflow and attach artifacts when available.
Use case: when you push a v* tag, the workflow builds, tags, and publishes the release with autogenerated notes.

Quick Start

Push a tag like v1.2.3 to trigger automatic release creation with autogenerated notes.

Frequently Asked Questions about Tag-based releases

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

FAQPage Schema

How do I automate GitHub releases with generated release notes?▼

To automate GitHub releases, you can use a workflow that triggers when you push a version tag. This skill automates the assembly, tagging, and publishing of releases while generating notes from commit messages and PR data.

What version tag pattern do I need to push to trigger an automatic GitHub release?▼

You need to push a tag that matches the v* pattern, such as v1.2.3. This action triggers the GitHub Actions workflow to automatically build, tag, and publish the release with autogenerated notes.

Does this automated release workflow require a specific GitHub Actions file?▼

Yes, the automation depends on a GitHub Actions workflow located at .github/workflows/release.yml. This file performs the actual release assembly, tagging, and publishing when a matching tag is pushed.

Can I attach build artifacts to an automatically generated GitHub release?▼

Yes, the workflow can attach artifacts to the release when they are available. It publishes the release via the GitHub Actions workflow and includes any artifacts generated during the build process.

Why should I use an automated tagging workflow instead of manual GitHub releases?▼

Manually creating GitHub releases for every tag is tedious and error-prone. Automating the process with this workflow ensures consistent release notes are generated automatically from commit messages and PR data.

When do I need an automated release workflow for my GitHub repository?▼

You need an automated release workflow when you want to publish consistent release notes without manual effort. It is triggered by pushing a v* tag, which builds and publishes the release automatically.