skills.rest
illogical
illogicalCOMMUNITY
Explore all skills by this author →
GitHub

changelog-generator

Generate user-facing release notes from Git commit history.

Updated Jan 19, 2026
Search Tags:#automation#git#changelog#release-notes#commit-history#customer-facing
One-click install
npx skills add https://github.com/illogical/InstructionLibrary --skill changelog-generator-illogical
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: changelog-generator
Source: https://github.com/illogical/InstructionLibrary/tree/main/skills/changelog-generator
Command: npx skills add https://github.com/illogical/InstructionLibrary --skill changelog-generator-illogical

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the transformation of raw git commits into customer-friendly release notes, saving time and improving transparency.

Core Features & Use Cases

  • Automated Scoping: Groups commits into features, improvements, bug fixes, and breaking changes.
  • Plain-language Summaries: Translates technical messages into user-facing language.
  • Release-ready Output: Formats entries suitable for public changelogs and product updates.

Quick Start

From your repository root, generate a changelog for the last release with a single command.

Frequently Asked Questions about changelog-generator

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

FAQPage Schema
How do I generate user-facing release notes from git commit history?▼

To generate release notes, the Skill processes your raw git commits and automatically groups them into features, improvements, bug fixes, and breaking changes, translating technical messages into plain-language summaries suitable for public changelogs.

What is the best way to turn technical git commits into customer-friendly changelogs?▼

The best way to turn technical git commits into customer-friendly changelogs is to automate the scoping of commits into categories and format the output into plain language, creating release-ready entries suitable for product updates and public release notes.

Can I format automated release notes for specific software version updates?▼

Yes, you can format automated release notes for specific software version updates by applying templated formatting to your git history, which structures entries by features, improvements, bug fixes, and breaking changes for sprints or versions.

Do I need direct access to my git repository to create automated changelogs?▼

Yes, you need access to your git commit history to create automated changelogs, as the Skill reads raw commit messages from the repository root to scope and translate them into release-ready product updates.

How does the changelog generator handle breaking changes versus regular bug fixes?▼

The changelog generator handles breaking changes and bug fixes by automatically scoping and grouping raw commits into distinct categories, ensuring breaking changes are clearly separated from regular bug fixes in the final release-ready output.

Related Skills

Explore More Product & Management Skills→
yocxy2yocxy2

gstack-openclaw-retro

Analyze git commit history to generate engineering retrospectives.

Community
Advanced
frostantfrostant
42

changelog-generator

Converts git commit history into categorized, ready-to-publish markdown release notes.

Community
Intermediate
asklarasklar
24

release

Determine semantic versions, create Git tags, and push to trigger CI releases.

Community
Intermediate
plurigridplurigrid
60

changelog-generator

Generate user-facing changelogs from git commit history.

Official
Advanced