skills.rest
jMerta
jMertaCOMMUNITY
Explore all skills by this author →
GitHub

release-notes

Generate Markdown release notes from git history and merged PRs.

130|15|Updated Dec 14, 2025
Search Tags:#automation#changelog#markdown#pull-requests#release-notes#git-history
One-click install
npx skills add https://github.com/jMerta/codex-skills --skill release-notes-jmerta
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-notes
Source: https://github.com/jMerta/codex-skills/tree/main/release-notes
Command: npx skills add https://github.com/jMerta/codex-skills --skill release-notes-jmerta

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Draft release notes and changelogs efficiently by extracting and summarizing changes from git history and merged PRs between two references.

Core Features & Use Cases

  • Range-based notes: Generate notes for a specific release range using from_ref..to_ref.
  • Change categorization: Automatically classify changes into Highlights, Breaking changes, Features, Fixes, and Docs.
  • Audience-ready output: Produce a clean Markdown document suitable for GitHub Releases, internal docs, or customer-facing changelogs.
  • Upgrade & migration notes: Include upgrade steps and compatibility notes when changes require user action.

Quick Start

Provide the release range (from_ref..to_ref) and a target version; the skill will produce a Markdown draft of the release notes ready for review.

Frequently Asked Questions about release-notes

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

FAQPage Schema
How do I generate release notes from git history and merged pull requests?▼

Generate release notes by summarizing git history and merged pull requests between two references. Provide a from_ref and to_ref range along with a target version to produce a clean Markdown draft ready for review.

What is the best way to categorize changes in a changelog automatically?▼

Automatically categorize changelog changes into Highlights, Breaking changes, Features, Fixes, and Docs. This classification organizes git history into structured Markdown suitable for user-facing release documentation.

Can I draft a GitHub Release from a specific commit range?▼

Yes, you can draft a GitHub Release from a specific commit range using the from_ref..to_ref syntax. The output is a Markdown document ready for GitHub Releases, internal docs, or customer-facing changelogs.

How do I include upgrade and migration notes in my release documentation?▼

Include upgrade and migration notes in release documentation by identifying changes that require user action. The generated changelog adds compatibility notes and upgrade steps alongside the categorized features and fixes.

Does this release notes generator work without external dependencies?▼

Yes, the release notes generator works without external dependencies. It relies solely on the provided git history and merged pull requests between your specified references to generate the Markdown output.

Related Skills

Explore More Content & Communication Skills→
highflame-aihighflame-ai
4

release-notes

Generate structured release notes from git commit history and pull requests.

Official
Advanced
zagarlucaszagarlucas

release-notes

Categorize tickets, PRDs, and changelogs into structured Markdown release notes.

Community
Intermediate
jikimejikime
5

jikime-workflow-changelog

Generate categorized changelogs from Git commits with breaking change detection.

Community
Advanced
allanninalallanninal
1

changelog-generator

Convert git commits into changelogs following Keep a Changelog and Conventional Commits.

Community
Intermediate