changelog

Generates Keep a Changelog formatted changelogs from git commit history since the last tag.

1|Updated Jan 31, 2026

Search Tags:#automation #git #changelog #documentation #commits #release notes

Ready to run

npx skills add https://github.com/jugrajsingh/skillgarden --skill changelog-jugrajsingh

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/jugrajsingh/skillgarden/tree/main/plugins/gitmastery/skills/changelog
Command: npx skills add https://github.com/jugrajsingh/skillgarden --skill changelog-jugrajsingh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of changelogs by parsing git commit history, ensuring consistent and informative release notes.

Core Features & Use Cases

Automated Changelog Generation: Creates changelogs based on git commits since the last tag.
Conventional Commit Mapping: Maps commit types (feat, fix, perf, etc.) to standard changelog sections (Added, Fixed, Changed).
Use Case: After releasing a new version of your software, use this Skill to quickly generate the CHANGELOG.md entry, saving manual effort and ensuring accuracy.

Quick Start

Run the changelog skill to generate the changelog since the last tag.

Frequently Asked Questions about changelog

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

FAQPage Schema

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

To generate a changelog from git commits, you can automate the process by parsing commit history since the last tag and mapping conventional commit types like feat and fix to standard sections in a CHANGELOG.md file.

What is the best way to format release notes from conventional commits?▼

Formatting release notes from conventional commits involves mapping commit types such as feat, fix, and perf to predefined Keep a Changelog sections like Added, Fixed, and Changed, ensuring structured and informative documentation.

How does automated changelog generation handle version suggestions?▼

Automated changelog generation handles version suggestions by analyzing the mapped change types from your git commits, prompting you for confirmation before applying the suggested version update to the changelog file.

Can I map git commit types to standard changelog sections without manual effort?▼

Yes, you can map git commit types to standard changelog sections without manual effort by using automation that recognizes conventional commit prefixes and places them into the correct Keep a Changelog categories.

Does this changelog automation require a specific git history format to work?▼

Changelog automation works best with conventional commit formats, parsing the git history since your last tag to accurately map commit types like fix and feat into the generated changelog sections.

Why does my generated changelog group commits into Added and Fixed categories?▼

Your generated changelog groups commits into Added and Fixed categories because it follows the Keep a Changelog format, mapping conventional commit types like feat to Added and fix to Fixed for clear, organized release notes.