Who this is for: Product managers, developers, and teams who need to turn git commits into polished, user-friendly changelogs without spending hours manually writing release notes.
What This Skill Does
Transforms technical git commits into clear, customer-friendly changelogs that users will actually understand and appreciate.
Core Capabilities
- Scans Git History — Analyzes commits from a specific time period or between versions
- Categorizes Changes — Groups commits into 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 with emojis and proper hierarchy
- Filters Noise — Excludes internal commits like refactoring, tests, and chore updates
- Follows Best Practices — Applies changelog guidelines and brand voice consistency
Usage
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
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
Tips
- Run from your git repository root for accurate commit history
- Specify date ranges for focused changelogs (weekly, monthly, per-release)
- Use a CHANGELOG_STYLE.md file for consistent formatting across releases
- Review and adjust the generated changelog before publishing
- Save output directly to CHANGELOG.md or your release notes file
Related Use Cases
- Creating GitHub release notes
- Writing app store update descriptions
- Generating email updates for users
- Creating social media announcement posts
- Maintaining a public changelog or product updates page