Changelog

Skill usrrname/agent-skills/skills/changelog

skill dump

Install

npx -y skills add usrrname/agent-skills --skill changelog

Assembled 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.

What its author says it does

Copied from the file, not written here

Generates a changelog by analyzing git history and tags. Use when the user asks to generate, write, or update a changelog.

SKILL.md

1.2 KB, as published. Nobody here has run it

Changelog Generation

Critical Rules

Analyze all git tags and categorize commits by type (feat, fix, docs, chore, etc.)
Create sections: Added, Fixed, Changed, Documentation
Include unreleased changes at the top
Store at project root as changelog.md
Follow Keep a Changelog format

Git Commands

git tag --sort=-version:refname                          # all tags (newest first)
git describe --tags --abbrev=0                           # most recent tag
git log --oneline --no-merges $(git describe --tags --abbrev=0 2>/dev/null || echo "")..HEAD  # unreleased
git log --oneline --no-merges <prev-tag>..<current-tag>  # between two tags

Filter by Conventional Commit Type

git log --oneline --grep="^feat:" <tag1>..<tag2>    # Features
git log --oneline --grep="^fix:" <tag1>..<tag2>     # Bug fixes
git log --oneline --grep="^docs:" <tag1>..<tag2>    # Documentation
git log --oneline --grep="BREAKING" <tag1>..<tag2>  # Breaking changes

Gives 2 of the 12 instructions most readme changelog skills give

Counted across 471 of the 478 authors here whose files we hold, read 2026-08-06

follow the Keep a Changelog formathere, and in 31 of 471, across 26 files
omit empty sectionsin 21 of 471
Run from the git repository rootin 20 of 471, across 7 files
save output directly to CHANGELOG.mdhere, and in 20 of 471, across 7 files
Group commits into logical categoriesin 19 of 471, across 6 files
Review the generated changelog before publishingin 19 of 471, across 6 files
Apply changelog guidelines and brand voicein 18 of 471, across 5 files
Exclude internal commits like refactoring and testsin 18 of 471, across 5 files
Specify date ranges for focused changelogsin 17 of 471, across 4 files
Convert technical commits into customer languagein 17 of 471, across 4 files
group commits by conventional commit typein 14 of 471
insert new entry below unreleased sectionin 14 of 471

Said here and by no other author read

analyze all git tags
create added fixed changed and documentation sections
include unreleased changes at the top

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.