release-notes

Compile release notes from git commit ranges and merged pull requests.

1|Updated Jun 17, 2026
One-click install
npx skills add https://github.com/Sfzmango/Maungs-agentic-toolbelt --skill release-notes-sfzmango
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-notes
Source: https://github.com/Sfzmango/Maungs-agentic-toolbelt/tree/main/plugins/maungs-agentic-toolbelt/skills/release-notes
Command: npx skills add https://github.com/Sfzmango/Maungs-agentic-toolbelt --skill release-notes-sfzmango

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually compiling release notes from scattered git commits, pull request metadata, and change logs is time-consuming, inconsistent, and often misses critical operational details like breaking changes, database migrations, or new environment variables that are essential for safe deployments.

Core Features & Use Cases

  • Auto-range detection: Automatically identifies the correct commit range to document (since the last git tag, last deploy marker, or merge-base with the default branch) so you don't have to manually specify SHAs.
  • PR-enriched classification: Pulls titles, labels, and bodies from merged GitHub PRs (via GitHub MCP or the gh CLI) to classify changes accurately by user impact, rather than relying solely on terse commit messages.
  • Multi-format output: Generates notes in markdown, compact deploy comments, Keep a Changelog entries, or GitHub release bodies to fit every step of your release workflow.
  • Operational risk surfacing: Prominently flags breaking changes, data migrations, and new required environment variables, and recommends an appropriate SemVer bump with clear justification.
  • Use case: For a team shipping a new payment processing feature, this skill automatically pulls all related commits and PRs, groups them into user-facing notes, flags the required database migration for transaction records, and recommends a minor version bump for the release.

Quick Start

Use the release-notes skill to generate human-facing release notes for all changes since the last git tag, formatted as a markdown document ready for your changelog.

Frequently Asked Questions about release-notes

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

FAQPage Schema
How do I automatically generate release notes from git commit history?

Automate release note generation by analyzing git commit ranges and merged pull requests to group changes into user-facing notes. This process classifies conventional commits, flags operational risks like database migrations, and outputs ready-to-use markdown changelog entries without manual transcription.

How do I prepare deployment comments that highlight breaking changes and data migrations?

Prepare deployment comments by surfacing breaking changes, data migrations, and new environment variables prominently from git logs and PR metadata. The generated deployment comments highlight operational risks and recommend an appropriate SemVer bump with clear justification for safe releases.

Can I generate Keep a Changelog entries directly from merged pull requests?

Generate Keep a Changelog entries directly from merged pull requests by pulling PR titles, labels, and bodies to classify changes by user impact. This PR-enriched classification ensures changelog entries reflect actual user-facing modifications rather than relying solely on terse commit messages.

What is the best way to determine a SemVer version bump from conventional commits?

Determine a SemVer version bump from conventional commits by analyzing commit ranges and PR metadata to identify breaking changes or new features. The analysis recommends an appropriate major, minor, or patch version increment with clear justification based on the classified changes.

Does this release notes generation method work without specifying specific commit SHAs?

Generate release notes without specifying commit SHAs through auto-range detection. The process automatically identifies the correct commit range to document by checking the last git tag, last deploy marker, or merge-base with the default branch, eliminating manual SHA specification.

How do I create GitHub release bodies from git tags and conventional commits?

Create GitHub release bodies from git tags and conventional commits by compiling the commit range since the last tag into multi-format output. This generates formatted GitHub release bodies that group related commits and pull requests into structured, user-facing release documentation.