changelog-generator

Generate structured markdown changelogs from categorized git commit histories.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/MaxKlat29/claude-setup --skill changelog-generator-maxklat29
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog-generator
Source: https://github.com/MaxKlat29/claude-setup/tree/main/skills/changelog-generator
Command: npx skills add https://github.com/MaxKlat29/claude-setup --skill changelog-generator-maxklat29

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill converts complex technical git commit logs into polished, human-readable changelogs that enhance communication with users and teams.

Core Features & Use Cases

  • Commit Analysis: Scans repository commit history within specific periods or versions.
  • Change Categorization: Organizes commits into categories like features, fixes, and improvements.
  • User-Friendly Output: Translates technical descriptions into accessible language for end-users.
  • Formatting: Produces professionally styled changelog entries suitable for documentation or release notes.
  • Filtering: Excludes internal, non-visible code changes like tests or refactoring to focus on user-impactful updates.
  • Use Cases: Generating release notes for new versions, weekly summaries, or public product updates.

Quick Start

Create a changelog to summarize all recent commits between versions.

Frequently Asked Questions about changelog-generator

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

FAQPage Schema
How do I generate readable release notes from git commit history?

To generate release notes from git commit history, this Skill parses commit messages and translates technical descriptions into accessible markdown. It automatically categorizes changes into features, fixes, and improvements for clear user communication.

Can I filter out internal code changes like refactoring when creating a changelog?

Yes, you can filter internal code changes when creating a changelog. The Skill excludes non-visible commits like tests or refactoring to ensure your changelog focuses strictly on user-impactful updates.

What is the best way to categorize git commits for product documentation?

The best way to categorize git commits for product documentation is to scan repository history and organize changes into distinct groups. This Skill automatically categorizes commits into features, fixes, and improvements to produce structured markdown output.

Does this changelog generator require any external dependencies to scan repositories?

No, this changelog generator requires no external dependencies to scan repositories. It works across entire repositories using built-in scripts and references to parse commit messages and generate structured markdown output without additional setup.

How do I summarize git commits between specific versions for a weekly update?

To summarize git commits between specific versions for a weekly update, the Skill analyzes repository commit history within defined periods. It transforms selected technical commits into polished, human-readable summaries suitable for internal updates or public communication.