Home
changelog-generator
davila7/claude-code-templates
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.
...Expand allAbout changelog-generator
The changelog-generator skill automatically transforms technical git commit messages into user-friendly changelogs that effectively communicate updates to customers and users. This skill addresses the common challenge of manually writing changelogs, which can be time-consuming and often results in technical jargon that may not be easily understood by the end users. By automating this process, changelog-generator not only saves valuable time but also ensures that the information presented is clear and accessible for all stakeholders involved.
FAQ
How do I create a changelog from my git repository?
You can create a changelog by running the skill from your project repository and specifying the desired time frame or version.
Is this skill compatible with all git repositories?
Yes, the changelog-generator can be used with any git repository that follows standard commit practices.
Are there any limitations in terms of commit types it can process?
The skill filters out internal commits such as refactoring and tests, focusing on user-facing changes.
Can I customize the format of the generated changelog?
Yes, you can use your own changelog style guidelines by referencing a CHANGELOG_STYLE.md file.
What is the best practice for running this skill?
It is recommended to run the skill from the root of your git repository and specify date ranges for focused changelogs.
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
- 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 → User-Friendly: Converts developer commits into customer language
- Formats Professionally: Creates clean, structured changelog entries
- Filters Noise: Excludes internal commits (refactoring, tests, etc.)
- 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 releaseGenerate changelog for all commits from the past weekCreate release notes for version 2.5.0With Specific Date Range
Create a changelog for all commits between March 1 and March 15With Custom Guidelines
Create a changelog for commits since v2.4.0, using my changelog guidelines from CHANGELOG_STYLE.mdExample
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
Install changelog-generator
Download and extract the skill files to your .claude/skills/ directory.
Download ZIPClone the repository and copy the skill files to your project.
git clone https://github.com/davila7/claude-code-templates/blob/main/cli-tool/components/skills/development/changelog-generator/SKILL.md # Copy SKILL.md to your .claude/skills/ directory
Copy
