What does changelog-generator do?

Automatically creates user-facing changelogs by analyzing git commits, categorizing changes, and translating technical commits into customer-friendly release notes.

Can I customize the formatting and brand voice?

Yes. You can follow the CHANGELOG_STYLE.md or provide custom guidelines to ensure consistency with your brand voice.

How does it handle noise or internal commits?

It filters out noise like internal commits (refactoring, tests) and allows targeting a specific date range or version for focused output.

changelog-generator

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-plugins/changelog-generator --openclaw

Files (1)

SKILL.md

2.9 KB

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 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

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

Source

git clone https://github.com/ComposioHQ/awesome-claude-plugins/blob/master/changelog-generator/skills/changelog-generator/SKILL.md

View on GitHub

Overview

Changelog Generator converts technical git commits into polished, user-friendly release notes. It analyzes commit history, groups changes into features, improvements, bug fixes, breaking changes, and security, translates developer language into customer-friendly text, and formats entries to brand guidelines, saving hours of manual work.

How This Skill Works

The tool scans git history within a specified window or between versions, categorizes changes, translates technical descriptions into customer-focused language, and applies clean, professional formatting while filtering out internal noise to produce publish-ready changelog entries.

When to Use It

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
Maintaining a public changelog or product updates page

Quick Start

Step 1: Run in your project repository to generate a changelog from commits since last release
Step 2: Optionally specify a date range or version tag for focused output
Step 3: Save the output to CHANGELOG.md and publish

Best Practices

Run from your git repository root to ensure accurate history
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 or your preferred location

Example Use Cases

Creating GitHub release notes with customer-friendly language
Writing app store update descriptions that highlight user impact
Generating email updates for users summarizing changes
Creating social media announcement posts from release notes
Generating update notifications for users and internal teams

Frequently Asked Questions

Add this skill to your agents