skills.rest
Barbaros911
Barbaros911COMMUNITY
Explore all skills by this author →
GitHub

changelog-generator

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

Updated Aug 12, 2026
Search Tags:#changelog#versioning#markdown#release notes#product updates#generate#git commits
One-click install
npx skills add https://github.com/Barbaros911/As-mine --skill changelog-generator-barbaros911
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: changelog-generator
Source: https://github.com/Barbaros911/As-mine/tree/main/.claude/skills/changelog-generator
Command: npx skills add https://github.com/Barbaros911/As-mine --skill changelog-generator-barbaros911

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing release notes from raw git commits is slow and produces developer jargon that customers cannot understand. This Skill automates the transformation of commit history into clear, customer-friendly changelogs. ## Core Features & Use Cases - Commit Analysis and Categorization: Scans git history for a date range or version span and groups commits into features, improvements, fixes, breaking changes, and security updates. - Technical-to-User Translation: Rewrites developer-oriented commit messages into plain customer language 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 structured Markdown changelog with emoji-labeled sections ready to publish. ## Quick Start Create a changelog from all 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 a changelog from git commits?▼

Run the request from your git repository root and specify a scope such as a date range, the past week, or commits since a version tag. The Skill scans the commit history, categorizes changes, and outputs a formatted Markdown changelog.

How to write release notes that customers understand?▼

Translate technical commit messages into outcome-focused customer language and group them into features, improvements, and fixes. This Skill performs that translation automatically and filters out internal commits like refactoring and tests.

Can I use a custom changelog style guide?▼

Yes, you can reference a style file such as CHANGELOG_STYLE.md in your request, and the generated changelog will follow your formatting guidelines and brand voice for consistency across releases.

Does the changelog include internal commits like tests and refactoring?▼

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

What are the limitations of automated changelog generation?▼

Output quality depends on commit message clarity, so vague commits may produce vague entries. You should review and adjust the generated changelog before publishing rather than treating it as final copy.

Related Skills

Explore More Product & Management Skills→
olli107xolli107x

changelog-generator

Generate structured changelogs from git history using conventional commit parsing.

Community
Intermediate
Kilo-OrgKilo-Org
166

changelog-generator

Generate user-facing changelogs from Git history with categorized release notes.

Official
Intermediate
cloudflarecloudflare
5.2k

conventions-check

Review pull request titles, descriptions, and scope against repository contribution conventions.

Official
Intermediate
vorynkavitaliyvorynkavitaliy

changelog-automation

Generate Keep a Changelog release notes from commits and PRs.

Community
Advanced