changelog-generator

Generate changelogs from Git commits in Markdown format.

33|5|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/Sir-chawakorn/power-ranger-toolkit --skill changelog-generator-sir-chawakorn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog-generator
Source: https://github.com/Sir-chawakorn/power-ranger-toolkit/tree/main/src/skills/changelog-generator
Command: npx skills add https://github.com/Sir-chawakorn/power-ranger-toolkit --skill changelog-generator-sir-chawakorn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of changelogs by parsing Git commits, saving developers significant time and ensuring consistent release notes.

Core Features & Use Cases

  • Conventional Commits Parsing: Understands commit messages formatted according to conventional standards (feat, fix, BREAKING CHANGE, etc.).
  • Automated Formatting: Generates changelogs in a clean Markdown format, including versioning and dates.
  • Use Case: After merging a new feature and several bug fixes, use this Skill to automatically update your CHANGELOG.md file with the latest changes, ready for your next release.

Quick Start

Use the changelog-generator skill to generate a new changelog entry based on recent commits.

Frequently Asked Questions about changelog-generator

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

FAQPage Schema
How do I automatically generate a changelog from conventional commits?

To automatically generate a changelog from conventional Git commits, you can use a changelog generator that parses commit types like feat, fix, and BREAKING CHANGE to produce clean Markdown release notes.

How does conventional changelog formatting handle release versioning?

Conventional changelog formatting handles release versioning by mapping Git commit types to standardized categories and grouping them under new version headers with dates in your CHANGELOG.md file.

What is the best way to update release notes after merging new features?

The best way to update release notes after merging new features is to automate changelog creation from Git commits, which parses your merged changes and formats them consistently for your next release.

Does this changelog generator work with standard-version and release-please?

Yes, this changelog generator provides examples and supports automation with tools like conventional-changelog, release-please, and standard-version to facilitate documentation updates for new releases.

Do I need to format my Git commits in a specific way to automate release notes?

Yes, you need to format your Git commits using conventional commit standards so the changelog generator can accurately parse commit messages and map them to the correct changelog sections.