changelog-generator

Generate user-facing changelogs from Git history with categorized release notes.

166|116|Updated Jan 19, 2026

Search Tags:#automation #git #changelog #versioning #documentation #release-notes

Ready to run

npx skills add https://github.com/Kilo-Org/kilo-marketplace --skill changelog-generator-kilo-org

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: changelog-generator
Source: https://github.com/Kilo-Org/kilo-marketplace/tree/main/skills/changelog-generator
Command: npx skills add https://github.com/Kilo-Org/kilo-marketplace --skill changelog-generator-kilo-org

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically converts developer commits into clear, customer-friendly release notes, saving hours of manual writing.

Core Features & Use Cases

Analyze Git history and group changes into features, improvements, bug fixes, breaking changes, and security
Translate technical commits into user-facing language
Format release notes with a professional structure suitable for publication
Exclude internal commits and noise
Provide guidelines and templates for consistent formatting

Quick Start

Generate 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 automatically generate release notes from Git commits?▼

Generate release notes from Git commits by analyzing version history to group changes into features, fixes, and breaking changes, then formatting them into customer-ready notes automatically.

How do I format Git commit history for a public changelog?▼

Format Git commit history for a public changelog by categorizing changes into features, improvements, bug fixes, and security updates, while filtering out internal commits and noise.

Can I create app store release notes from Git history?▼

Yes, you can create app store release notes from Git history by processing commits within a versioned release or time-bounded window and translating technical changes into user-facing language.

How do I categorize breaking changes and security updates in a changelog?▼

Categorize breaking changes and security updates in a changelog by analyzing Git history to identify and group specific commit types into distinct professional publication categories.

How do I exclude internal commits when generating version documentation?▼

Exclude internal commits when generating version documentation by filtering Git history noise, ensuring only customer-facing changes are aggregated into the final release notes.

What is the best way to automate changelog creation for product updates?▼

Automate changelog creation for product updates by analyzing Git history to group changes by category and formatting them with professional templates suitable for publication.