release

Name: release
Availability: InStock
Author: MakerLabs

Automate Specflow releases by bumping versions, tagging, and pushing to main.

Updated Apr 22, 2026

Search Tags:#automation #git #release #semver #ci #github-releases #version-bump

Ready to run

npx skills add https://github.com/mkrlabs/specflow --skill release-mkrlabs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release
Source: https://github.com/mkrlabs/specflow/tree/main/.claude/skills/release
Command: npx skills add https://github.com/mkrlabs/specflow --skill release-mkrlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the release management workflow for Specflow, handling version bumps, commits, tags, and pushes so releases are consistent and reproducible.

Core Features & Use Cases

Bump the version semver according to patch/minor/major/prerelease semantics.
Commit, tag, and push changes to main to trigger the GitHub Actions release workflow.
Generate a structured changelog and assemble release artifacts across all target binaries.

Quick Start

Run the release process in the Specflow repository after choosing a bump type.

Frequently Asked Questions about release

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

FAQPage Schema

How do I automate version bumps and GitHub releases for my repository?▼

Automating GitHub releases involves bumping the semver version, committing the change, tagging the release, and pushing to the main branch to trigger CI workflows. This ensures deterministic version management and consistent publishing.

What's the best way to trigger a GitHub Actions release workflow with a semver tag?▼

Triggering a GitHub Actions release workflow requires pushing a new semver tag to the main branch. The release process commits version bumps and applies the tag, which automatically initiates the downstream publishing workflow.

Can I publish a prerelease version using automated release management?▼

Yes, automated release management supports prerelease versions alongside patch, minor, and major bumps. It tags the prerelease and pushes it to the main branch, ensuring the CI pipeline is green before publishing.

Does automated release management require CI checks to pass before tagging?▼

Yes, the release process ensures CI checks are green before tagging and pushing changes to the main branch. This prevents broken releases and guarantees that only verified code is published to GitHub Releases.

How does automated changelog generation work during a version bump?▼

Changelog generation during a version bump assembles structured release notes based on the new semver tag. The release process commits these notes alongside the version bump before pushing the tag to trigger the GitHub Actions workflow.

When should I avoid using an automated release process for version management?▼

You should avoid automated release processes if your workflow does not rely on a single main branch or if you need to manually control tag creation. This automation specifically targets deterministic tagging and pushing to trigger CI pipelines.