release-notes

Categorize Git commit logs into structured release notes in Markdown.

3|Updated Mar 31, 2026

Search Tags:#automation #git #changelog #formatting #commits #release-notes

Ready to run

npx skills add https://github.com/sunny0826/open-source-skills --skill release-notes-sunny0826

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release-notes
Source: https://github.com/sunny0826/open-source-skills/tree/main/skills/release-notes
Command: npx skills add https://github.com/sunny0826/open-source-skills --skill release-notes-sunny0826

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate structured Release Notes / Changelog from a raw commit log. Automatically categorizes commits into Breaking Changes, Features, and Fixes, helping teams communicate changes clearly.

Core Features & Use Cases

Automatically classify commit messages into Breaking Changes, Features, and Bug Fixes, ignoring noise like chore or docs-only updates.
Produce a clean, publication-ready Markdown document that can be released to stakeholders or included in release notes.
Support bilingual output (English or Chinese) based on user language input and context.

Quick Start

Paste the raw commit logs or changelog text and ask me to generate a release notes document.

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 commit history?▼

Categorize git commits into Breaking Changes, Features, and Bug Fixes by pasting raw commit logs. The tool ignores noise like chore or docs updates and outputs a structured Markdown changelog ready for stakeholders.

Can I create a bilingual changelog from raw commit messages?▼

Yes, you can create a bilingual changelog from raw commit messages. The tool supports bilingual output, generating structured release notes in English or Chinese based on your language input.

What is the best way to format raw commit logs into a structured changelog?▼

The best way to format raw commit logs into a structured changelog is using an automated categorization tool. It classifies commits into Breaking Changes, Features, and Fixes, ignoring noise like chore updates, and outputs a publication-ready Markdown document.

Does the release notes generator ignore chore and docs commits?▼

Yes, the release notes generator ignores chore and docs commits. It filters out this noise automatically, ensuring the final Markdown changelog only highlights Breaking Changes, Features, and Bug Fixes.

What do I need to prepare before generating release notes from git commits?▼

Prepare your raw commit logs or changelog text to generate release notes. Paste this text into the tool to automatically categorize and format it into a structured Markdown document.