PluginBench
Skill
Fail
Audit score 45

changelog-generator

composiohq/awesome-claude-skills

Transform git commits into polished, customer-friendly release notes automatically.

What is changelog-generator?

This skill analyzes git commit history, categorizes changes, and converts technical commits into clear, user-facing changelogs. Use it when preparing release notes, documenting product updates, or creating release announcements.

  • Scans git history for a specific time period or between versions
  • Categorizes commits into features, improvements, bug fixes, breaking changes, and security updates
  • Translates technical developer language into customer-friendly descriptions
  • Formats output as professionally structured changelog entries
  • Filters out internal commits like refactoring and tests
  • Applies changelog best practices and brand voice consistency

How to install changelog-generator

npx skills add https://github.com/composiohq/awesome-claude-skills --skill changelog-generator
Prerequisites
  • Git repository with commit history
  • Access to the project repository root
Claude Code
Cursor
Windsurf
Cline

How to use changelog-generator

  1. 1.Run the skill from your git repository root directory
  2. 2.Specify the date range or version range for commits to include (e.g., past 7 days, since v2.4.0)
  3. 3.Optionally provide a CHANGELOG_STYLE.md file for custom formatting guidelines
  4. 4.Review the generated changelog output
  5. 5.Adjust or refine entries as needed before publishing
  6. 6.Save the output to CHANGELOG.md or your release notes destination

Use cases

Good for
  • Preparing release notes for a new software version
  • Creating weekly or monthly product update summaries
  • Writing changelog entries for app store submissions
  • Generating GitHub release notes and announcements
  • Creating internal release documentation and email updates
Who it's for
  • Product managers
  • Release engineers
  • DevOps teams
  • Open source maintainers
  • Product marketing teams

changelog-generator FAQ

Can I use this for commits between specific versions?

Yes. Specify the version range (e.g., 'since v2.4.0') and the skill will analyze commits between those versions.

How do I maintain consistent formatting across releases?

Create a CHANGELOG_STYLE.md file with your formatting guidelines and pass it to the skill. It will apply your brand voice and structure consistently.

Does it filter out internal commits?

Yes. The skill automatically excludes internal commits like refactoring, tests, and other non-user-facing changes.

What output formats does it support?

The skill generates markdown-formatted changelogs that can be saved to CHANGELOG.md, used in GitHub releases, or adapted for other platforms.

Can I use this for different time periods?

Yes. You can generate changelogs for specific date ranges, the past week, the past month, or between any two git references.

Full instructions (SKILL.md)

Source of truth, from composiohq/awesome-claude-skills.


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

  1. Scans Git History: Analyzes commits from a specific time period or between versions
  2. Categorizes Changes: Groups commits into logical categories (features, improvements, bug fixes, breaking changes, security)
  3. Translates Technical → User-Friendly: Converts developer commits into customer language
  4. Formats Professionally: Creates clean, structured changelog entries
  5. Filters Noise: Excludes internal commits (refactoring, tests, etc.)
  6. 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