changelog-generator

Generate Markdown changelogs from categorized Git commit history.

7|1|Updated Jan 14, 2026

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

Ready to run

npx skills add https://github.com/eyadsibai/ltk --skill changelog-generator-eyadsibai

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: changelog-generator
Source: https://github.com/eyadsibai/ltk/tree/main/plugins/ltk-github/skills/changelog-generator
Command: npx skills add https://github.com/eyadsibai/ltk --skill changelog-generator-eyadsibai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of converting raw Git commit messages into polished, human-readable changelogs or release notes, saving developers time and improving communication.

Core Features & Use Cases

Commit Analysis: Scans Git history to identify changes between specified versions, dates, or tags.
Categorization: Groups commits into predefined categories like "New Features," "Improvements," and "Bug Fixes."
Translation: Converts technical commit messages into clear, user-centric language.
Formatting: Outputs changelogs in a structured Markdown format.
Use Case: Automatically generate release notes for your next software update by analyzing commits made since the last release, categorizing them, and presenting them in a user-friendly format for your customers.

Quick Start

Generate a changelog from commits made since the last Git tag.

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

To generate release notes from Git commit history, you can analyze commits within specified ranges or tags, categorize them into features, improvements, and bug fixes, and translate technical messages into user-friendly Markdown output.

How do I convert technical Git commits into customer-facing changelogs?▼

Converting technical Git commits into customer-facing changelogs involves scanning commit history between versions, grouping changes into categories like "New Features" and "Bug Fixes," and translating developer jargon into clear language for users.

Can I generate a changelog for commits between two specific Git tags?▼

Yes, you can generate a changelog for commits between two specific Git tags by analyzing the commit history within that specified range, categorizing the changes, and formatting the translated output into a structured Markdown document.

What is the best way to automate software versioning documentation from commits?▼

Automating software versioning documentation from commits is done by scanning Git history to identify changes since the last release, grouping them into predefined categories, and formatting the translated results into a structured Markdown format.

Does this changelog generator require specific commit message formats to categorize features and bug fixes?▼

The changelog generator analyzes Git commit history and categorizes commits into features, improvements, and bug fixes. It translates technical commit messages into clear language, though the metadata does not specify a required commit message format.

What format does the generated changelog output use?▼

The generated changelog output uses a structured Markdown format. It categorizes analyzed Git commits into features, improvements, and bug fixes, and presents the translated user-centric language in this structured Markdown document.