| 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. |
Changelog Generator
This skill transforms technical git commits into polished, user-friendly changelogs that users will actually understand.
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 or 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 to User-Friendly: Converts developer commits into customer language
- Formats Professionally: Creates clean, structured changelog entries
- Filters Noise: Excludes internal commits (refactoring, tests, CI/CD, etc.)
- Follows Best Practices: Applies changelog guidelines and the project's voice
How to Use
Basic Usage
Create a changelog from commits since last release
Generate changelog for all commits from the past week
Create release notes for version X.Y.Z
With Specific Date Range
Create a changelog for all commits between [start date] and [end date]
With Custom Guidelines
If a changelog style guide exists at CHANGELOG_STYLE.md:
Create a changelog for commits since vX.Y.Z, using changelog
guidelines from CHANGELOG_STYLE.md
Output Format
# Updates — [Period or Version]
## New Features
- **[Feature Name]**: [User-facing description of what it does
and why it matters]
## Improvements
- **[Area]**: [What improved and how it affects users]
## Fixes
- [User-facing description of what was broken and that it's fixed]
Tips
- Run from the git repository root
- Specify date ranges for focused changelogs
- Use
CHANGELOG_STYLE.md for consistent formatting if one exists
- 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
Generated by autoharness | Template: community/skills/changelog-generator/SKILL.md.tmpl