skills.rest
gmolike
gmolikeCOMMUNITY
Explore all skills by this author →
GitHub

changelog-generator

Generate user-facing changelogs by analyzing and categorizing git commit history.

Updated Mar 4, 2026
Search Tags:#changelog#versioning#release notes#product updates#generate#git commits
One-click install
npx skills add https://github.com/gmolike/Claude-Template --skill changelog-generator-gmolike
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: changelog-generator
Source: https://github.com/gmolike/Claude-Template/tree/main/.agents/skills/changelog-generator
Command: npx skills add https://github.com/gmolike/Claude-Template --skill changelog-generator-gmolike

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing release notes from raw git commits is tedious and time-consuming, and technical commit messages rarely make sense to end users. This Skill automates the transformation of developer commits into clear, customer-friendly changelogs. ## Core Features & Use Cases - Commit Analysis & Categorization: Scans git history for a date range or version span and groups commits into features, improvements, bug fixes, breaking changes, and security updates. - Technical-to-User Translation: Rewrites developer-oriented commit messages into language customers understand, while filtering out internal noise like refactoring and test commits. - Use Case: Before shipping version 2.5.0, ask for release notes covering all commits since v2.4.0 and receive a formatted Markdown changelog with emoji-labeled sections ready to publish. ## Quick Start Ask the assistant to create a changelog from all commits since the last release in your repository.

Frequently Asked Questions about changelog-generator

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

FAQPage Schema
How do I generate a changelog from git commits?▼

Run the request from your repository root and specify a time period or version range, such as all commits since the last release. The Skill scans the git history, categorizes changes, and outputs a formatted Markdown changelog.

How to write release notes that users actually understand?▼

Translate technical commit messages into customer-focused language describing the benefit, not the implementation. This Skill automates that translation and groups entries into features, improvements, and fixes.

Can I generate a changelog for a specific date range?▼

Yes, you can specify any date range, such as commits between March 1 and March 15, or a version span like commits since v2.4.0. The Skill filters git history accordingly before categorizing changes.

Does the changelog include internal commits like refactoring?▼

No, internal commits such as refactoring, tests, and chore work are filtered out as noise. Only user-relevant changes like features, improvements, bug fixes, breaking changes, and security updates appear in the output.

Can I customize the changelog format and tone?▼

Yes, you can provide your own guidelines file such as CHANGELOG_STYLE.md, and the Skill will follow your formatting conventions and brand voice when generating entries.

Related Skills

Explore More Product & Management Skills→
yannicklothyannickloth

commit

Stage and commit working tree changes as logically grouped commits.

Community
Intermediate
javierbadapalacio6-beepjavierbadapalacio6-beep

changelog-generator

Generates user-facing changelogs from git commit history by categorizing and rewriting commits.

Community
Basic
yashtekavadeyashtekavade

changelog-maintenance

Generate CHANGELOG.md sections, release notes, and breaking-change migration guides.

Community
Intermediate
smart-village-solutionssmart-village-solutions
4

changelog-automation

Generate changelogs from commits, PRs, and releases using Keep a Changelog.

Official
Intermediate