generate-changelog

Name: generate-changelog
Availability: InStock
Author: maslennikov-ig

Generate Keep a Changelog–compliant Markdown sections from git commits, plan files, or manual entries.

243|40|Updated Nov 11, 2025

Search Tags:#git #planning #changelog #releases

Ready to run

npx skills add https://github.com/maslennikov-ig/claude-code-orchestrator-kit --skill generate-changelog-maslennikov-ig

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: generate-changelog
Source: https://github.com/maslennikov-ig/claude-code-orchestrator-kit/tree/main/.claude/skills/generate-changelog
Command: npx skills add https://github.com/maslennikov-ig/claude-code-orchestrator-kit --skill generate-changelog-maslennikov-ig

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill creates Keep a Changelog–style sections from git commits, plan files, or manual entries.

Core Features & Use Cases

Convention mapping: Map commit types to Added/Fixed/Changed/Security categories.
Grouping & deduping: Consolidates changes by category and removes duplicates.
Plan-driven updates: Integrates changes listed in plan files for release notes.

Quick Start

Generate a changelog for version 0.8.0 from recent commits.

Frequently Asked Questions about generate-changelog

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

FAQPage Schema

How do I generate a changelog from git commits?▼

Generate a changelog by parsing git commits using conventional commit conventions, which map commit types to categories like Added, Fixed, Changed, and Security. The Skill extracts commits between versions, groups them by category, removes duplicates, and formats output as a Keep a Changelog–compliant Markdown section.

What's the best way to create release notes automatically?▼

Automate release notes by feeding git history, plan files, or manual entries into a changelog generator that enforces version, date, and source inputs. It consolidates changes by category and produces formatted Markdown sections ready for documentation.

Can I generate a CHANGELOG.md from plan files?▼

Yes. The Skill supports plan-file sources alongside git commits and manual entries, integrating planned changes into release notes. It parses all source types, categorizes entries, and outputs Keep a Changelog–formatted Markdown sections.

Does this work with conventional commits?▼

Conventional commits are the primary input mechanism. The Skill maps commit types (feat, fix, chore, etc.) to changelog categories, groups related commits, deduplicates entries, and formats them into Keep a Changelog sections.

What happens if I have duplicate changes across versions?▼

The Skill deduplicates changes within a changelog entry by consolidating identical modifications across commits and sources. Grouped by category, duplicates are merged into a single entry to keep release notes concise.

What inputs do I need to provide?▼

Provide version, release date, a source type (git, plan-file, or manual), and source data. The Skill validates these required inputs and handles error cases for empty or invalid data before generating output.