changelog-generator

Name: changelog-generator
Availability: InStock
Author: greenmamba29

Generate structured CHANGELOG.md entries from git commit history and semantic versioning tags.

Updated Feb 18, 2026

Search Tags:#automation #git #changelog #versioning #documentation #commits

Ready to run

npx skills add https://github.com/Greenmamba29/skillsdotmd_web --skill changelog-generator-greenmamba29

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: changelog-generator
Source: https://github.com/Greenmamba29/skillsdotmd_web/tree/main/.agents/skills/changelog-generator
Command: npx skills add https://github.com/Greenmamba29/skillsdotmd_web --skill changelog-generator-greenmamba29

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation and updating of CHANGELOG.md files, ensuring consistency with Keep a Changelog conventions and semantic versioning.

Core Features & Use Cases

Automated Changelog Generation: Creates structured changelog entries from git commit history.
Conventional Commits Parsing: Understands and categorizes commits (feat, fix, chore, etc.).
PR Integration: Incorporates PR titles and descriptions for richer context.
Semantic Versioning: Automatically bumps version numbers based on change types.
Use Case: After a development cycle, use this skill to generate the next release's changelog section, automatically grouping new features, bug fixes, and other changes.

Quick Start

Generate the changelog for version 2.1.0 based on commits since version 2.0.0.

Frequently Asked Questions about changelog-generator

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

FAQPage Schema

How do I generate a changelog from git commit history automatically?▼

You can generate a changelog from git commit history by parsing conventional commit messages to group changes by type, formatting entries according to Keep a Changelog standards, and automatically bumping semantic version numbers based on the change types detected.

What is the best way to structure a CHANGELOG.md from conventional commits?▼

The best way to structure a CHANGELOG.md from conventional commits is to categorize messages by prefixes like feat, fix, and chore, grouping them into Added, Changed, and Fixed sections to comply with Keep a Changelog conventions.

Can I use PR descriptions to add context to an automated changelog?▼

Yes, automated changelog generation can incorporate PR titles and descriptions to provide richer context alongside standard git commit history, ensuring the resulting CHANGELOG.md entries accurately reflect development changes.

How does semantic versioning auto-bumping work with changelog generation?▼

Semantic versioning auto-bumping works by analyzing parsed conventional commit messages during changelog generation, automatically incrementing the version number based on the highest change type detected, such as a major bump for breaking changes.

Does changelog generation work without semantic versioning tags in my repository?▼

Changelog generation relies on semantic versioning tags in your repository to determine commit ranges for each release, so missing tags prevent accurate version comparison and structured entry creation for the CHANGELOG.md file.