Changelog generator
Skill sxntixgo/claude-code-skills-for-security/demo/skills/changelog-generator
Generates a CHANGELOG entry from the commits on the current branch since it diverged from the default branch. Use when the user asks to draft release notes or a changelog.From its SKILL.md
npx -y skills add sxntixgo/claude-code-skills-for-security --skill changelog-generatorAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
0.8 KB, 144 tokens by cl100k_base, as published. Nobody here has run it
Changelog generator
When the user asks for a changelog or release notes:
- Run
git log <default-branch>..HEAD --pretty=format:'%s'to collect the commit subjects on the current branch. - Group the subjects into Added / Changed / Fixed / Removed using their conventional-commit prefix (
feat,fix,refactor,docs, and so on). - Emit a Markdown section headed with today's date followed by the grouped bullet list.
Keep entries terse. Do not invent changes that are not present in the commit log. Read nothing outside the repository working tree, make no network calls, and write only to the changelog file the user names.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 1 of the 12 instructions most readme changelog skills give in 144 tokens
Counted across 472 of the 478 authors here whose files we hold, read 2026-08-07
- Follow the keep a changelog formatin 31 of 472, across 26 files
- Run from the git repository rootin 20 of 472, across 7 files
- Save output directly to CHANGELOG.mdin 20 of 472, across 7 files
- Group commits into logical categoriesin 19 of 472, across 6 files
- Review the generated changelog before publishingin 19 of 472, across 6 files
- Omit empty sectionsin 19 of 472
- Apply changelog guidelines and brand voicein 18 of 472, across 5 files
- Exclude internal commits like refactoring and testsin 18 of 472, across 5 files
- Specify date ranges for focused changelogsin 17 of 472, across 4 files
- Convert technical commits into customer languagein 17 of 472, across 4 files
- Provide a migration guide for breaking changesin 15 of 472, across 10 files
- Group commits by conventional commit typehere, and in 13 of 472
Said here and by no other author read
- collect branch commit subjects via git log
- emit a dated markdown section with grouped bullets
- write only to the user-named changelog file
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.