changelog-generator

Use it when:: You're writing release notes, an app store update or a weekly product update from recent commits.
It does:: Reads the git history for a date range or since a version, groups the changes and rewrites them for customers.
You get:: A Markdown changelog with sections such as new features, improvements and fixes, for you to review before publishing.
Leaves out:: Internal commits such as refactoring and tests.
Follows:: Your own changelog style guide, such as a CHANGELOG_STYLE.md, when you point it to one.

TL;DR

You run it from the repository and say which commits to cover: since the last release, the past week, a date range or a version. The agent scans those commits, sorts them into features, improvements, bug fixes, breaking changes and security, drops internal work, and translates developer phrasing into what changed for the user, in your brand voice or your style file's format. The example output is a dated update with short bold-titled entries under emoji headings. It suggests reviewing the result before publishing, and saving it to CHANGELOG.md, and lists other uses such as GitHub release notes, app store descriptions, update emails and announcement posts.

Summarizes the skill at be2a406.

npx skills add https://github.com/ComposioHQ/awesome-claude-skills --skill changelog-generator

skills.sh page Source on GitHub All skills from ComposioHQ/awesome-claude-skills

Total Downloads: 7,600 on skills.sh, Nov 9, 2026
Repo stars: 79,081 ComposioHQ/awesome-claude-skills
First seen: Jan 20, 2026 on skills.sh

Weekly Downloads

138

+13% over the 8 weeks to Nov 9

Weekly values

Week to	Installs
Sep 21	122
Sep 28	125
Oct 5	173
Oct 12	143
Oct 19	143
Oct 26	140
Nov 2	132
Nov 9	138

Category	category:writing category:engineering category:software-engineering Articles, docs, internal comms, research write-ups and prose that doesn't read as generated. Test-first work, implementation from specs, git hygiene and scope control. Everything for building software: planning, coding, debugging, design, frameworks, cloud, agents and skills.
Type	type:command A one-shot action you invoke by name, such as turning the conversation into a PRD.
Effect	effect:none Adds no side effects of its own. It shapes how the agent thinks, writes or reviews. Guidelines and routers are always effect:none, even when the task they support edits code.
Needs	needs:none Instructions only. Works in any agent that supports skills.
Publisher	by:official A verified publisher on skills.sh, or the company or maintainer behind the product the skill operates.
Topics	git docs-writing
Stack	stack:git

SKILL.md

From ComposioHQ/awesome-claude-skills at be2a406. Checked daily, last changed Nov 6, 2026.

Frontmatter

name: changelog-generator
description: Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

Changelog Generator

This skill transforms technical git commits into polished, user-friendly changelogs that your customers and users will actually understand and appreciate.

When to Use This Skill

Preparing release notes for a new version
Creating weekly or monthly product update summaries
Documenting changes for customers
Writing changelog entries for app store submissions
Generating update notifications
Creating internal release documentation
Maintaining a public changelog/product updates page

What This Skill Does

Scans Git History: Analyzes commits from a specific time period or between versions
Categorizes Changes: Groups commits into logical categories (features, improvements, bug fixes, breaking changes, security)
Translates Technical → User-Friendly: Converts developer commits into customer language
Formats Professionally: Creates clean, structured changelog entries
Filters Noise: Excludes internal commits (refactoring, tests, etc.)
Follows Best Practices: Applies changelog guidelines and your brand voice

How to Use

Basic Usage

From your project repository:

Create a changelog from commits since last release

Generate changelog for all commits from the past week

Create release notes for version 2.5.0

With Specific Date Range

Create a changelog for all commits between March 1 and March 15

With Custom Guidelines

Create a changelog for commits since v2.4.0, using my changelog 
guidelines from CHANGELOG_STYLE.md

Example

User: "Create a changelog for commits from the past 7 days"

Output:

# Updates - Week of March 10, 2024

## ✨ New Features

- **Team Workspaces**: Create separate workspaces for different 
  projects. Invite team members and keep everything organized.

- **Keyboard Shortcuts**: Press ? to see all available shortcuts. 
  Navigate faster without touching your mouse.

## 🔧 Improvements

- **Faster Sync**: Files now sync 2x faster across devices
- **Better Search**: Search now includes file contents, not just titles

## 🐛 Fixes

- Fixed issue where large images wouldn't upload
- Resolved timezone confusion in scheduled posts
- Corrected notification badge count

Inspired by: Manik Aggarwal's use case from Lenny's Newsletter

Tips

Run from your git repository root
Specify date ranges for focused changelogs
Use your CHANGELOG_STYLE.md for consistent formatting
Review and adjust the generated changelog before publishing
Save output directly to CHANGELOG.md

Related Use Cases

Creating GitHub release notes
Writing app store update descriptions
Generating email updates for users
Creating social media announcement posts