changelog-from-commits
SolidUse when cutting a release, writing a CHANGELOG entry, or summarizing what changed since a tag — when the repo's commits follow (or mostly follow) Conventional Commits and a mechanically-accurate section breakdown beats a model's reading of the diff.
Install
Quality Score: 84/100
Skill Content
Details
- Author
- Rtur2003
- Repository
- Rtur2003/Claude-Code-Promts-Skills
- Created
- 8 months ago
- Last Updated
- 6 days ago
- Language
- Python
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
changelog
Generate a changelog or release notes from Git history, grouped by change type, written in user-facing language, with issue/PR links and breaking changes called out. Conventional-Commits aware and Keep a Changelog formatted; respects any existing CHANGELOG or tooling. Use when preparing release notes or updating CHANGELOG.md.
changelog
Generates or updates CHANGELOG.md from Conventional Commits since the last tag (Keep a Changelog format, SemVer bump proposal). Use before a release.
changelog
Turn git history since the last release into a human-readable changelog or release notes, grouped by type of change and written for the people who use the software, not the people who wrote it. Use this whenever the user is cutting a release, asks for release notes, a changelog, "what changed since the last version", wants to update CHANGELOG.md, or is tagging a version. Also use when someone needs to summarize a range of commits into something a user or stakeholder would read.