changelog

Generate changelogs and release notes from Git history using conventional commits.

3|Updated Feb 6, 2026

Search Tags:#automation #changelog #versioning #release #semver #conventional-commits #keepachangelog

Ready to run

npx skills add https://github.com/1Mangesh1/dev-skills-collection --skill changelog-1mangesh1

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/1Mangesh1/dev-skills-collection/tree/main/skills/changelog
Command: npx skills add https://github.com/1Mangesh1/dev-skills-collection --skill changelog-1mangesh1

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Changelog generation and release documentation are time-consuming tasks that this skill automates, ensuring accurate, up-to-date CHANGELOG.md entries.

Core Features & Use Cases

Automated Unreleased and versioned sections generation following Keep a Changelog and semantic versioning.
Conventional commits parsing to categorize changes (feat, fix, docs, style, refactor, perf, etc.).
Release notes automation across single or multi-package repos, with migration notes and pre-release support.

Quick Start

Run the generator to create a CHANGELOG.md from recent commits using conventional commits.

Frequently Asked Questions about changelog

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

FAQPage Schema

How do I automate changelog generation from conventional commits?▼

Automate changelog generation by parsing Git history for conventional commits to categorize changes like feat, fix, or refactor. This process automatically produces structured Unreleased and versioned sections in your CHANGELOG.md.

Does this changelog generator support the Keep a Changelog format and semantic versioning?▼

Yes, it supports the Keep a Changelog format and semantic versioning. It automatically structures your release notes into Unreleased and versioned sections, including support for pre-release versions and migration notes.

Can I generate release notes for multi-package repos using Git history?▼

Yes, you can generate release notes for multi-package repos. The generator parses Git history to automate release documentation across multiple packages while maintaining a clean CHANGELOG.md format.

What is the best way to maintain a clean CHANGELOG.md for software projects?▼

The best way is to automate it by parsing conventional commits from Git history. This categorizes changes automatically and applies the Keep a Changelog structure to ensure accurate, up-to-date entries.

How do conventional commits categorize changes in automated release notes?▼

Conventional commits categorize changes by parsing commit message prefixes like feat, fix, docs, style, refactor, and perf. This allows the generator to automatically organize entries into appropriate sections.

Are migration notes and pre-release versions supported in automated changelogs?▼

Yes, migration notes and pre-release versions are supported. The generator applies semantic versioning to produce versioned sections that include these specific release details.