change-writer
Generates clean, human-readable changelogs and release notes from git commits and file changes. Use when preparing for a release or summarizing recent work.
When & Why to Use This Skill
The Change Writer skill automates the generation of structured, human-readable changelogs and release notes by analyzing git commit history and file modifications. It streamlines the software documentation process by intelligently categorizing updates into features, bug fixes, and performance improvements, ensuring clear and professional communication for stakeholders and users.
Use Cases
- Release Management: Automatically generate professional Markdown release notes for GitHub or GitLab releases based on recent commit history and version tags.
- Work Summarization: Quickly summarize recent development progress for daily stand-ups or weekly stakeholder reports to highlight key technical achievements and bug resolutions.
- Documentation Maintenance: Keep project CHANGELOG.md files consistently updated by analyzing staged or unstaged changes before finalizing a release cycle.
- Audit and Compliance: Create a clear, chronological record of repository changes to assist in security audits or internal reviews of code evolution.
| name | change-writer |
|---|---|
| description | Generates clean, human-readable changelogs and release notes from git commits and file changes. Use when preparing for a release or summarizing recent work. |
Change Writer Skill
This skill analyzes recent changes in the repository to generate structured changelogs. It categorizes changes into Features, Fixes, and Refactors.
Instructions
- Analyze History: Run the git log command to see recent changes.
- Identify Impact: Look at changed files to understand the scope (e.g., UI, logic, infrastructure).
- Draft Notes: Group changes by type (Feat, Fix, Chore, Docs).
- Format: Output in Markdown format compatible with
CHANGELOG.mdor GitHub Releases.
Categories
- 🚀 Features: New functionality.
- 🐛 Bug Fixes: Resolving issues.
- ⚡ Performance: Speed optimizations.
- 🧹 Chores: Internal tasks, dependency updates.
- 📝 Documentation: Changes to docs.
Example Output
## [1.2.0] - 2025-12-27
### 🚀 Features
- Added `Zustand` store for global theme management.
- Implemented `api-expert` skill for better backend integration.
### 🐛 Bug Fixes
- Fixed keyboard avoiding view overlap on Android.
- Resolved race condition in auth flow.
### 🧹 Chores
- Updated `expo` to SDK 54.
- Cleaned up unused assets.
Run scripts/get-changes.sh to see a summary of unstaged changes.