wiki-changelog
Generate Changelogs from Git History
Manually compiling changelogs from git history is time-consuming and error-prone. This skill automatically analyzes commit history and generates structured, categorized changelogs organized by change type and time period.
Download the skill ZIP
Upload in Claude
Go to Settings → Capabilities → Skills → Upload skill
Toggle on and start using
Test it
Using "wiki-changelog". Generate a changelog for the past week
Expected outcome:
## Changelog - Last 7 Days
### Features 🆕
- Add user authentication flow (2024-01-15)
- Implement password reset functionality (2024-01-14)
### Fixes 🐛
- Resolve login redirect issue on mobile (2024-01-13)
- Fix timezone handling in date picker (2024-01-12)
### Documentation 📝
- Update API documentation with new endpoints (2024-01-11)
### Dependencies 📦
- Upgrade React to v18.2.0 (2024-01-10)
Using "wiki-changelog". What changed in the last month? Include breaking changes.
Expected outcome:
## Changelog - Last 30 Days
### Breaking Changes ⚠️
- **Migration Required**: Rename `User.getProfile()` to `User.profile()` - update all references
- **Migration Required**: API v2 endpoints now require authentication header
### Features 🆕
- Multiple new features listed...
### Fixes 🐛
- Multiple bug fixes listed...
Security Audit
SafeStatic analysis flagged 4 high-risk patterns related to 'weak cryptographic algorithm' at lines 3, 22, 27, and 32. This is a FALSE POSITIVE - the skill contains no cryptographic code. The analyzer misidentified common words in the markdown documentation. The skill is a simple changelog generator that reads git log data and produces structured output. No network calls, no external commands, no file writes, no environment access.
Detected Patterns
Quality Score
What You Can Build
Generate Release Notes
Quickly produce release notes by analyzing recent commits and categorizing all changes since the last release.
Track Project Activity
Understand what has changed in a project over time by viewing a structured summary of recent development activity.
Onboard Team Members
Help new team members understand recent changes and the current state of the project through organized changelogs.
Try These Prompts
Use the wiki-changelog skill to generate a changelog for this repository. What changes have been made recently?
Generate a changelog for version X.X.X release. Include all features, bug fixes, and any breaking changes.
Analyze the git history and provide a weekly summary of all changes, grouped by category like features, fixes, and documentation updates.
Generate a changelog that highlights all breaking changes and includes migration notes for upgrading.
Best Practices
- Ensure commit messages follow a consistent convention (Conventional Commits recommended) for accurate categorization
- Review generated changelogs before publishing to ensure terminology matches project standards
- Use the skill regularly (weekly or before each release) to maintain up-to-date changelogs
Avoid
- Do not rely solely on automated categorization - verify that commits are grouped correctly
- Avoid using vague commit messages like 'fix', 'update', 'changes' which reduce changelog usefulness
- Do not skip reviewing breaking changes - always verify migration notes are accurate