mstack-release

Analyze merged PRs since the last git tag and generate changelog entries with semver version bumps.

3|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/Abhilash-003/mstack --skill mstack-release
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mstack-release
Source: https://github.com/Abhilash-003/mstack/tree/main/release
Command: npx skills add https://github.com/Abhilash-003/mstack --skill mstack-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes the manual, error-prone work of preparing changelogs, determining version bumps, tagging releases, and publishing GitHub releases—while keeping you in control of destructive actions.

Core Features & Use Cases

  • Release planning from merged PRs: Analyzes merged pull requests since the last tag and categorizes them into features, fixes, docs, internal changes, and breaking changes.
  • Version bump + changelog generation: Chooses the next semver version (including user confirmation for first release), then drafts a Keep-a-Changelog-style entry (or matches the existing format).
  • Tagging and GitHub release publication with approvals: Creates the changelog/version artifacts, commits them, creates an annotated git tag, and publishes the GitHub release, with explicit confirmation steps before shipping and before pushing.

Quick Start

Run mstack-release to analyze merged PRs since the last tag and walk you through approving the release, tagging, and GitHub publication.

Frequently Asked Questions about mstack-release

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

FAQPage Schema
How do I automate GitHub release preparation from merged pull requests?

Automate GitHub release preparation by analyzing merged pull requests since the last git tag, categorizing changes, and generating a changelog entry with an appropriate semver version bump. The process requires authenticated gh CLI access and local git history to compute the previous and next tags.

How does semantic versioning work when generating a changelog from git tags?

Semantic versioning determines the next version bump by analyzing merged PRs categorized into features, fixes, docs, internal changes, and breaking changes. It then drafts a Keep-a-Changelog-style entry or matches the existing changelog format preserved in the repository.

Can I use this approach to bootstrap a first release for a repository?

Yes, first-release bootstrapping is supported by interactively requesting user confirmation for the initial semantic version. It then generates the initial changelog and creates the first annotated git tag before publishing the GitHub release.

Do I need to manually approve git tagging and pushing during release automation?

Explicit interactive user approvals are required before destructive actions like committing, tagging, and pushing. This guardrail ensures you maintain control over shipping while the release automation handles the changelog generation and GitHub release publication.

What's the best way to preserve an existing changelog format during automated release tagging?

To preserve an existing changelog format during automated release tagging, the process optionally reads configuration files to match formatting rules. It drafts Keep-a-Changelog-style entries that align with the repository's established documentation structure.

Why does automated release automation require local git history and gh CLI access?

Automated release automation requires local git history to compute the last tag and analyze merged PRs, and authenticated gh CLI access to publish the GitHub release. Without these dependencies, the tool cannot accurately determine semantic version bumps or create annotated tags.