Create Changelog
ListedAutomatically generates concise, formatted changelogs from commit messages and issue tracking data.
Install on your platform
create-changelog. cowork-os/cowork-os has no skill named "create-changelog" any more. It was renamed, moved or deleted upstream.We check each listing against its upstream repository with the rules the skills CLI uses, last on 2026-10-22. We don't show a command we know will fail.
What we know about this skill
Publisher
cowork-os
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
We could not read this skill's source, so none of the checks below were run.
About this skill
What it does
This skill automatically generates changelogs from commit messages. It parses a repository's commit history, extracts relevant information from each commit message, and formats it into a structured changelog document. The resulting changelog can be easily integrated into release notes or other documentation.
When to use it
- After completing a series of software development commits that need summarizing for a release.
- To automatically maintain a project's changelog alongside ongoing development.
- When needing to quickly generate a summary of changes made in a repository for stakeholders.
- For creating versioned documentation from commit history.
Key capabilities
- Parses Git commit messages.
- Extracts information from commits.
- Formats extracted data into changelog documents.
Example prompts
- "Generate a changelog for the
my-projectrepository." - "Create a changelog from the last 10 commits in this repository."
- “Summarize changes made between version 1.0 and 2.0 of my project.”
Tips & gotchas
The quality of the generated changelog depends heavily on well-formatted commit messages. Ensure your team follows consistent commit message conventions for best results.