Changelog

Skill nanocodana/nanocodana/packages/cli/example-skills/changelog

Write a clear CHANGELOG entry from the staged git changesFrom its SKILL.md

Install

npx -y skills add nanocodana/nanocodana --skill changelog

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

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, 180 tokens by cl100k_base, as published. Nobody here has run it

Changelog Skill

Produce a concise, user-facing CHANGELOG entry for the current change.

Steps

Inspect what changed (read the diff; use the Grep/Read tools, or git diff --staged via host Bash if needed).
Group changes into Added / Changed / Fixed / Removed.
Write entries from the user's perspective — what they can now do or what broke — not the internal implementation.
Keep each bullet to one line; lead with a verb.

Format

## [Unreleased]
### Added
- <feature, user-facing>
### Fixed
- <bug, what was wrong before>

Rules

No internal jargon or file paths in the entries.
Omit empty sections.
One entry per meaningful change; don't pad.

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 180 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 sectionshere, and in 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 typein 13 of 472

Said here and by no other author read

inspect the staged diff

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.