Demo

Skill Systemartis/readmedaddy/skills/readmedaddy/eval/fixtures/skill-fixture/skills/demo

Use when a release is being cut and the CHANGELOG is empty, stale, or out of sync with the commits since the last tag; when commit messages need to be turned into human-readable release notes grouped by type; or when asked to "update the changelog", "write release notes", or "what changed since the last release". Not a version bumper and not a tag/publisher; yields to an existing changelog format already in the repo.From its SKILL.md

Install

npx -y skills add Systemartis/readmedaddy --skill demo

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

8 stars8 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 file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.8 KB, 304 tokens by cl100k_base, as published. Nobody here has run it

changelog-scribe

changelog-scribe turns the commit range since the last release tag into a clean, grouped CHANGELOG section: features, fixes, and breaking changes, each as a reader-facing line rather than a raw commit subject. It follows Keep a Changelog ordering and never invents an entry that has no commit behind it.

Method

Find the range. Resolve the latest release tag and collect commits from that tag to HEAD. If there is no tag, use the full history and say so.
Classify each commit. Bucket into Added / Changed / Fixed / Removed / Deprecated / Security from the commit type and body, dropping noise commits (merges, formatting-only, CI tweaks).
Rewrite for readers. Convert each kept commit into a present-tense, user- facing line. A commit subject is a developer note; a changelog line is for the person upgrading.
Assemble the section. Emit a dated ## [version] block in the repo's existing changelog order, breaking changes first and called out explicitly.
Verify. Every line traces back to a real commit in the range. Nothing is added that the diff does not support.

What's in references/

references/grouping.md — the commit-type to changelog-section mapping and the noise-commit filter rules.

What ships with it: 1 file

816 B alongside SKILL.md

references/

grouping.md816 B

Gives 1 of the 12 instructions most readme changelog skills give in 304 tokens

Counted across 446 of the 460 authors here whose files we hold, read 2026-09-06

Follow Keep a Changelog formatin 24 of 446
Collect commits since the last git taghere, and in 15 of 446, across 13 files
Omit empty sectionsin 14 of 446
Put breaking changes first with migration stepsin 14 of 446
Include migration guidance for breaking changesin 11 of 446, across 10 files
Categorize commits by conventional commit prefixin 11 of 446
Mark breaking changes prominentlyin 10 of 446
Prepend the new entry to CHANGELOG.mdin 9 of 446
Highlight breaking changes with migration notesin 8 of 446, across 7 files
Classify changes into Keep a Changelog categoriesin 8 of 446, across 7 files
Group related commits into single entriesin 8 of 446
Write the changelog from commitsin 8 of 446

Said here and by no other author read

Use full history when no tag exists
Drop merge, formatting-only, and CI commits
Emit a dated version block
Follow the repo's existing changelog order

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.