changelog-generator

Convert git commit history into customer-friendly changelogs with categorized changes.

Updated Feb 15, 2026

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

Ready to run

npx skills add https://github.com/ricable/mcai --skill changelog-generator-ricable

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: changelog-generator
Source: https://github.com/ricable/mcai/tree/main/.agents/skills/changelog-generator
Command: npx skills add https://github.com/ricable/mcai --skill changelog-generator-ricable

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual effort of turning raw git commits into clear, customer-friendly changelogs, release notes, and product update summaries.

Core Features & Use Cases

Commit Scanning: Reviews commit history for a release window, version range, or custom date range.
Change Categorization: Groups work into features, improvements, fixes, breaking changes, and security updates.
User-Friendly Rewrite: Converts developer language into polished messaging that customers can understand.
Use Case: A product team can generate weekly release notes from recent commits, filter out noisy internal changes, and publish a concise update page in minutes.

Quick Start

Use the changelog-generator skill to create a customer-friendly changelog from the commits since your last release.

Frequently Asked Questions about changelog-generator

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

FAQPage Schema

How do I generate release notes from git commit history?▼

To generate release notes, you can use the changelog-generator to scan your git commit history for a specific version range or date window, automatically categorizing and rewriting commits into professional customer-facing updates.

Can I automatically convert git commits into customer-friendly changelogs?▼

Yes, you can automatically convert raw git commits into customer-friendly changelogs by filtering out noisy internal changes and rewriting developer language into clear, polished messaging for product update summaries.

What is the best way to categorize code changes for weekly product updates?▼

The best way to categorize code changes for weekly product updates is to group commits by features, improvements, fixes, breaking changes, and security updates, ensuring the final release notes align with your chosen style guide.

Does the changelog generator work for app store submission release notes?▼

Yes, the changelog generator works for app store submissions by analyzing your commit history, filtering out internal noise, and formatting the remaining changes into concise, professional release documentation.

How do I filter out internal noise when creating a changelog from commits?▼

You can filter out internal noise when creating a changelog by scanning your commit history for a specific release window and applying change categorization to exclude irrelevant developer language from the final release notes.