release-notes-generator

Classify merged changes between version references into release note categories.

47|2|Updated Jun 3, 2026
One-click install
npx skills add https://github.com/Amazon-Quick/Amazon-Quick-official-catalog --skill release-notes-generator-amazon-quick
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-notes-generator
Source: https://github.com/Amazon-Quick/Amazon-Quick-official-catalog/tree/main/skills/release-notes-generator
Command: npx skills add https://github.com/Amazon-Quick/Amazon-Quick-official-catalog --skill release-notes-generator-amazon-quick

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates human-readable release notes by collecting merged PRs and commits across version ranges, classifying changes, and rendering them into a chosen format for distribution and documentation.

Core Features & Use Cases

  • Collects merged changes between two references from any supported VCS platform or pasted data.
  • Classifies changes by type (Breaking Changes, Features, Bug Fixes, Performance, Documentation, Internal/Chores) and renders grouped notes for stakeholders, engineers, or public releases.
  • Outputs in multiple formats: markdown, platform_release, chat_post, or wiki, with breaking changes surfaced prominently and links to source data.

Quick Start

Provide the source data, specify from_ref and to_ref, and choose an output format to generate release notes.

Frequently Asked Questions about release-notes-generator

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

FAQPage Schema
How do I generate release notes from merged commits between two versions?

To generate release notes from merged commits, provide the source data, specify the starting and ending version references, and choose an output format. The tool collects merged changes across that range and classifies them into standard categories.

Can I create a changelog in markdown from version control changes?

Yes, you can create a changelog in markdown from version control changes by selecting the markdown output format. It groups changes by type and surfaces breaking changes prominently while preserving original titles and linking to source data.

What output formats are supported for release notes besides markdown?

Besides markdown, supported release notes output formats include platform_release, chat_post, and wiki. Each format renders grouped changes appropriately for stakeholders, engineers, or public distribution channels.

How are breaking changes surfaced when generating release notes?

Breaking changes are surfaced first and prominently at the top of the generated release notes. The tool classifies changes by type, ensuring breaking changes are separated from features, bug fixes, performance improvements, and documentation.

Does the release notes generator work with pasted data if I don't have a VCS platform connected?

Yes, the release notes generator works with pasted data if you do not have a VCS platform connected. It can operate against any supported VCS platform or directly process pasted data to identify and classify merged changes.

What is the best way to classify code changes for a public release?

The best way to classify code changes for a public release is using an automated generator that categorizes merged PRs and commits into breaking changes, features, bug fixes, performance, and documentation, excluding skipped entries to produce clean notes.