changelog-generator

Convert git commit history into categorized, user-friendly changelog sections.

1|1|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/corticalstack/claude-code-flow --skill changelog-generator-corticalstack
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog-generator
Source: https://github.com/corticalstack/claude-code-flow/tree/main/.claude/skills/changelog-generator
Command: npx skills add https://github.com/corticalstack/claude-code-flow --skill changelog-generator-corticalstack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing user-facing changelogs from raw git commits is slow and error-prone, and developer-focused commit messages often don’t translate well into release notes customers can understand.

Core Features & Use Cases

  • Scans Git History: Analyzes commits from a chosen time period or between versions to establish what changed.
  • Categorizes Changes: Groups commits into clear buckets like new features, improvements, bug fixes, breaking changes, and security updates.
  • Translates Technical to User-Friendly: Rewrites developer-oriented wording into customer-appropriate language while excluding common noise like internal refactors and test-only commits.

Quick Start

Run this skill from your git repository root and ask it to create a changelog for commits since the 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 commits?

To generate release notes from git commits, the skill scans your repository history across a date range or between tags, categorizes changes into features and fixes, and formats them into user-friendly release notes.

Can I create a changelog between two specific version tags?

Yes, you can create a changelog between two specific version tags by running the skill from your git repository root and asking it to select commits across the defined version range or release period.

What is the best way to write app store release notes from technical commit messages?

The best way to write app store release notes from technical commit messages is to translate developer-oriented wording into customer-appropriate language while filtering out internal noise like refactors and test-only commits.

How are git commits categorized in generated changelogs?

Git commits are categorized in generated changelogs by grouping them into clear buckets such as new features, improvements, bug fixes, breaking changes, and security updates.

Does the changelog generator filter out internal refactoring commits?

Yes, the changelog generator filters out internal noise by excluding common internal refactors and test-only commits to ensure the final release notes focus on user-facing changes.

Can I use this for weekly product update summaries?

Yes, you can use this for weekly product update summaries by scanning the git commit history from the chosen time period and formatting the changes into a polished, categorized changelog.