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.
cd ~/.claude/skills
git clone https://github.com/ComposioHQ/awesome-claude-skills.git awesome-claude-skills mkdir -p ~/.claude/skills/changelog-generator
curl -fsSL https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/HEAD/changelog-generator/SKILL.md \
-o ~/.claude/skills/changelog-generator/SKILL.md This skill transforms technical git commits into polished, user-friendly changelogs that your customers and users will actually understand and appreciate.
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
Create a changelog for all commits between March 1 and March 15
Create a changelog for commits since v2.4.0, using my changelog
guidelines from CHANGELOG_STYLE.md
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
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Use when executing implementation plans with independent tasks in the current session
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when implementing any feature or bugfix, before writing implementation code
Use when creating new skills, editing existing skills, or verifying skills work before deployment