home / skills / questnova502 / claude-skills-sync / changelog-generator

changelog-generator skill

/skills/changelog-generator

This skill generates polished user-facing changelogs from git commits, converting technical messages into clear release notes.

npx playbooks add skill questnova502/claude-skills-sync --skill changelog-generator

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
3.0 KB
---
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**:
```markdown
# 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

Overview

This skill automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and converting technical notes into clear, customer-friendly release notes. It turns hours of manual changelog writing into minutes by filtering noise and applying consistent formatting and brand voice. Use it to generate polished release notes, update summaries, or app store descriptions quickly.

How this skill works

The tool scans your git history for a specified range or between tags, extracts commit messages, and groups them into categories such as features, improvements, bug fixes, breaking changes, and security. It translates developer-centric language into concise, user-focused bullets, filters out internal noise (refactors, tests), and formats the result into a structured changelog ready for publishing. You can provide custom guidelines or a style file to match your brand voice and formatting rules.

When to use it

  • Preparing release notes for a new version or patch
  • Creating weekly or monthly product update summaries
  • Generating app store update descriptions or GitHub release notes
  • Documenting customer-facing changes after a sprint or milestone
  • Maintaining a public changelog or update feed

Best practices

  • Run the generator from your repository root to ensure full commit context
  • Specify tags or date ranges to focus the changelog on the relevant scope
  • Provide a CHANGELOG_STYLE.md or similar guidelines to keep tone and formatting consistent
  • Review and edit the generated content before publishing to confirm accuracy and priorities
  • Exclude or mark internal-only commits in your commit messages to improve output quality

Example use cases

  • Create release notes for version 2.5.0 from commits since the last tag
  • Generate a weekly update for customer email summarizing new features and fixes
  • Produce concise app store release text highlighting user-facing improvements
  • Compile a public changelog page from all commits in the last month
  • Create an internal release summary that separates breaking changes and migrations

FAQ

Can it ignore internal commits like tests or refactors?

Yes. The generator filters common internal commit types by default and can be customized to ignore additional patterns or scopes.

How do I preserve my brand voice and formatting?

Provide a style guide file or example changelog (e.g., CHANGELOG_STYLE.md) and the tool will apply those rules when translating and formatting entries.