Changelog Generation

Name: Changelog Generation
Availability: InStock
Author: Kolb

Parse Git commit history into structured Markdown and JSON changelogs.

Updated Aug 23, 2026

Search Tags:#automation #git #changelog #versioning #semantic-versioning #release-notes #commit-analysis

Ready to run

npx skills add https://github.com/mkolb22/zen-plugin --skill changelog-generation-mkolb22

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Changelog Generation
Source: https://github.com/mkolb22/zen-plugin/tree/main/skills/changelog-generation
Command: npx skills add https://github.com/mkolb22/zen-plugin --skill changelog-generation-mkolb22

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically generate structured release notes and changelogs from Git history, ensuring consistency with semantic versioning and reducing manual toil across teams.

Core Features & Use Cases

Conventional commit parsing and automatic semantic versioning mapping.
Structured changelog generation with sections for features, fixes, docs, and breaking changes.
Version tagging, date stamping, and multi-format outputs (Markdown and JSON) for release processes.

Quick Start

Run the skill on your repository to generate a structured CHANGELOG.md from the latest commits.

Frequently Asked Questions about Changelog Generation

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

FAQPage Schema

How do I generate a changelog from git commits automatically?▼

Generate changelogs from Git history by parsing conventional commits to categorize entries into features, fixes, and breaking changes, then output structured Markdown or JSON release notes.

How does conventional commit parsing work for semantic versioning?▼

Conventional commit parsing maps commit messages to semantic version bumps by categorizing entries into features, fixes, docs, and breaking changes to determine the correct version increment.

Can I output release notes in both Markdown and JSON formats?▼

Yes, the skill produces both Markdown and JSON changelog outputs with version tags and dates aligned to semantic versioning rules for seamless release process integration.

What is the best way to automate semantic versioning from commit history?▼

Automate semantic versioning by parsing Git commit history to map conventional commits to version bumps, generating structured changelogs with categorized release notes and version tags.

Do I need to follow conventional commits to generate structured release notes?▼

Yes, your Git commit history must use conventional commit formatting so the parser can accurately map entries to semantic version bumps and categorize them for structured changelogs.

Why does my automatically generated changelog separate breaking changes from fixes?▼

Generated changelogs separate breaking changes from fixes because conventional commit parsing categorizes entries into distinct sections to align with semantic versioning rules for accurate release notes.