changelog-generator

Generate user-facing changelogs from git commit history.

5|Updated Feb 26, 2026

Search Tags:#automation #git #changelog #documentation #commits #release notes

Ready to run

npx skills add https://github.com/lidge-jun/cli-jaw-skills --skill changelog-generator-lidge-jun

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: changelog-generator
Source: https://github.com/lidge-jun/cli-jaw-skills/tree/main/changelog-generator
Command: npx skills add https://github.com/lidge-jun/cli-jaw-skills --skill changelog-generator-lidge-jun

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of user-facing changelogs from git commit history, transforming technical commits into clear, customer-friendly release notes.

Core Features & Use Cases

Scans Git History: Analyzes commits within a specified period or between versions.
Categorizes Changes: Groups commits into features, improvements, bug fixes, etc.
Translates Technical → User-Friendly: Converts developer commits into customer-readable language.
Use Case: Automatically generate release notes for your next software update by analyzing all commits made since the last release.

Quick Start

Create a changelog from commits since the last release.

Frequently Asked Questions about changelog-generator

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

FAQPage Schema

How do I generate release notes from git commit history?▼

You can generate release notes from git commit history by scanning commits since your last release, categorizing them into features, improvements, and bug fixes, and translating technical commits into customer-friendly language. The Skill filters out internal commits to produce clean, user-facing changelogs.

How do I translate technical git commits into user-friendly changelogs?▼

You translate technical git commits into user-friendly changelogs by analyzing commit history and converting developer-centric messages into customer-readable release notes. The Skill automatically categorizes changes into features, improvements, bug fixes, and breaking changes for non-technical audiences.

Can I filter out internal commits when creating a changelog from git history?▼

Yes, you can filter out internal commits when creating a changelog from git history. The Skill scans your specified commit period and removes internal commits, ensuring only customer-facing changes like features, improvements, and bug fixes are included in the generated release notes.

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

You categorize git commits into features, improvements, and bug fixes for documentation by analyzing your commit history and automatically grouping changes into distinct categories. The Skill also identifies breaking changes and translates all categorized commits into user-friendly release notes.

Does the changelog generator work with specific commit formats or conventions?▼

The changelog generator analyzes git commit history within a specified period or between versions, categorizing changes into features, improvements, and bug fixes. It translates technical commits into customer-friendly release notes and filters out internal commits regardless of specific commit conventions.

What is the best way to automate changelog creation from commits for my next software release?▼

The best way to automate changelog creation from commits is to scan your git history since the last release. The Skill categorizes changes into features, improvements, and bug fixes, and translates technical commits into clear, customer-friendly release notes for your next software update.