Release Notes Generator

Convert git log output or PR titles into categorized Markdown release notes.

9|1|Updated Mar 15, 2026

Search Tags:#automation #git #changelog #documentation #markdown #pr #release-notes

Ready to run

npx skills add https://github.com/Notysoty/openagentskills --skill release-notes-generator-notysoty

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Release Notes Generator
Source: https://github.com/Notysoty/openagentskills/tree/main/skills/release-notes-generator
Command: npx skills add https://github.com/Notysoty/openagentskills --skill release-notes-generator-notysoty

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates clear, user-facing release notes from raw git logs or PR lists, saving time and ensuring consistency.

Core Features & Use Cases

Groups changes by category (New Features, Improvements, Bug Fixes, Breaking Changes) for clear, user-facing release notes.
Translates technical commit messages or PR titles into plain-English summaries.
Formats output as Markdown ready for GitHub Releases, CHANGELOG.md, or blog posts.
Supports multiple input formats (git log, PR titles/descriptions) and outputs publication-ready notes.

Quick Start

Create a release notes draft by running the tool on your latest git history and pasting the output into your release page.

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 git log output?▼

Generating release notes from git log output involves parsing commit history, grouping changes by category, and rewriting technical messages into plain-English summaries formatted as Markdown for GitHub Releases or CHANGELOG.md.

Can I create a changelog from PR titles for GitHub Releases?▼

Yes, creating a changelog from PR titles is supported by parsing pull request data, grouping entries into categories like New Features and Bug Fixes, and formatting the results into publication-ready Markdown for GitHub Releases.

What is the best way to group git commits into categories for documentation?▼

Grouping git commits into categories for documentation requires parsing raw commit messages or PR titles, classifying them into New Features, Improvements, Bug Fixes, or Breaking Changes, and outputting a structured Markdown template.

How do I convert technical commit messages into plain-English release notes?▼

Converting technical commit messages into plain-English release notes requires parsing git history, translating developer-centric language into user-facing summaries, and formatting the text into Markdown according to a structured template.

Does the release notes automation support multiple input formats like git log and PR lists?▼

Yes, release notes automation supports multiple input formats including raw git log output and PR titles or descriptions, parsing them to produce user-facing Markdown formatted for GitHub Releases, CHANGELOG.md, or blog posts.