release-notes

Generate structured RELEASE_NOTES.md from categorized Git history.

2|Updated Jan 23, 2026

Search Tags:#automation #git #changelog #templating #release-notes #contributors

Ready to run

npx skills add https://github.com/kangminhyuk1111/agents --skill release-notes-kangminhyuk1111

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

An automated method to convert Git history into structured release notes, saving time and ensuring consistent documentation.

Core Features & Use Cases

Automatically categorize commits into Features, Bug Fixes, Improvements, and Documentation for a polished changelog.
Identify contributors and assemble a concise overview for release credits.
Use a Git tag range or an explicit range to generate a precise RELEASE_NOTES.md aligned with your release.

Quick Start

Run the release-notes skill in your repository to generate RELEASE_NOTES.md from the current git history.

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 automatically?▼

To generate release notes from git history, this Skill analyzes your commit log and categorizes entries into features, fixes, improvements, and documentation, then outputs a structured RELEASE_NOTES.md file using a predefined template with the confirmed version and date.

What is the best way to scope commits for a changelog using Git tags?▼

Scoping commits for a changelog using Git tags is handled by determining the version range directly from existing tags or explicit user input, ensuring only the relevant changes for that specific release are included in the generated notes.

Can I identify contributors from git commits for release credits?▼

You can identify contributors from git commits because the Skill parses the commit history to assemble a concise overview of contributors, providing proper release credits within the final RELEASE_NOTES.md output.

How do I categorize git commits into features and bug fixes for documentation?▼

Categorizing git commits into features and bug fixes is accomplished by analyzing the commit messages in your repository history, automatically sorting them into structured sections for a polished and consistent changelog.

Do I need to provide a specific version range to generate a changelog?▼

You do not need to manually provide a version range to generate a changelog if Git tags exist, as the Skill can automatically determine the scope from tags, though explicit range input is supported for precise scoping.