release

Automate release notes, changelogs, and signed git tags.

10|1|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/thoreinstein/beads-workflow --skill release-thoreinstein
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/thoreinstein/beads-workflow/tree/main/skills/release
Command: npx skills add https://github.com/thoreinstein/beads-workflow --skill release-thoreinstein

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the authoring of release artifacts by standardizing the creation of release notes, changelogs, and signed release tags, reducing manual coordination and human error.

Core Features & Use Cases

  • Release Notes & Changelog: Generate structured notes from commits, PRs, and changes since the last release.
  • Versioning & Tagging: Determine the appropriate semantic version and create a signed Git tag for the release.
  • Stakeholder Communication: Prepare release artifacts for distribution and team communication.

Quick Start

Use the release skill to draft release notes from the latest commits, assemble the changelog, and sign a new Git tag for the upcoming version.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate git tag creation and changelog generation for software releases?

Automating git tag creation and changelog generation requires standardizing release artifacts from commits and PRs. This Skill drafts structured release notes, determines semantic versions, and creates signed Git tags to reduce manual coordination and human error.

What's the best way to generate release notes from recent commits automatically?

Generating release notes from recent commits involves extracting changes since the last release. This Skill automates authoring structured notes and changelogs from commit history, preparing them for stakeholder communication and distribution.

Do I need signed commits and tags to automate my release process?

Signed commits and tags are required for disciplined release automation and artifact integrity. This Skill applies multi-step verification and generates signed Git tags to satisfy requirements for secure software distribution and traceable versioning.

Can I use semantic versioning automation for projects with multi-step verification?

Semantic versioning automation supports projects requiring multi-step verification and artifact generation. This Skill determines the appropriate semantic version from project changes and applies pre-flight checks before creating the signed release tag.

Why does manual release coordination lead to changelog errors and inconsistent tagging?

Manual release coordination causes changelog errors and inconsistent tagging due to human oversight. Automating release artifact authoring standardizes the creation of release notes and signed tags, applying pre-flight checks to eliminate manual coordination failures.