changelog

Generate Keep a Changelog changelogs from git commits and conventional commit messages.

10|2|Updated Nov 11, 2025
One-click install
npx skills add https://github.com/toilahuongg/Shopify-Agents-Kit --skill changelog-toilahuongg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/toilahuongg/Shopify-Agents-Kit/tree/main/.claude/skills/changelog
Command: npx skills add https://github.com/toilahuongg/Shopify-Agents-Kit --skill changelog-toilahuongg

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the creation and maintenance of changelogs, ensuring consistency and saving developers time by analyzing git commits and adhering to established standards.

Core Features & Use Cases

  • Automated Changelog Generation: Creates changelogs based on git commit history, following the Keep a Changelog format.
  • Conventional Commits Integration: Maps conventional commit types (feat, fix, etc.) to changelog categories.
  • Version Bumping: Suggests appropriate semantic version bumps (major, minor, patch) based on commit types.
  • Use Case: After releasing a new feature and fixing a bug, use this skill to automatically update your CHANGELOG.md file with the latest changes and the correct version number.

Quick Start

Generate the changelog for unreleased changes.

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 conventional commits?

Generate a changelog from conventional commits by analyzing git history and mapping commit types like feat and fix to Keep a Changelog categories. This process categorizes changes into Added, Changed, Fixed, Security, Deprecated, and Removed sections automatically.

Can I automate semantic version bumps based on git commit history?

Yes, you can automate semantic version bumps by analyzing git commit history. The process evaluates conventional commit types to suggest appropriate major, minor, or patch version increments for your release notes.

What is the Keep a Changelog format for release notes?

The Keep a Changelog format for release notes is a standardized structure that organizes version updates into specific categories: Added, Changed, Fixed, Security, Deprecated, and Removed, ensuring consistent documentation of project changes.

Does this changelog generator output Markdown and JSON formats?

Yes, this changelog generator supports output formatting in both Markdown and JSON. It parses your git commits and conventional commit messages to produce structured release notes in your preferred format.

How do I group unreleased git commits into changelog categories?

Group unreleased git commits into changelog categories by parsing conventional commit messages. The mechanism maps commit prefixes directly to Keep a Changelog sections, automatically sorting your unreleased changes for the changelog.