Write a Tegami changelog entry (`.tegami/<slug>.md`). Use when finishing a change that ships in a published package — a feature, fix, or breaking refactor — or when asked for a changelog entry, changeset, or release note.
Installs into .claude/skills of the current project.
Sponsors
SSkills DirectorySkills Directory
Know which skills are safe — weekly.
SSkills DirectorySkills Directory
Is that skill safe to install?
Are you the author of Changelog?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/gkurt-changelog)
---
name: changelog
description: Write a Tegami changelog entry (`.tegami/<slug>.md`). Use when finishing a change that ships in a published package — a feature, fix, or breaking refactor — or when asked for a changelog entry, changeset, or release note.
---
# Changelog entries
Releases are managed by [Tegami](https://tegami.fuma-nama.dev) (config in
`scripts/tegami.mts`). Every change that ships needs an entry — run
`bun run tegami`, or write `.tegami/<slug>.md` yourself:
```md
---
packages:
"<pkg>": patch
---
### Menu rows light up under the pointer
```
- The body needs at least one heading. Tegami silently drops an entry without one.
- One sentence under the heading, often none — the heading is usually the whole entry.
- Don't bump `version` in `package.json` — the entry is the bump. Tegami applies it
in the release workflow's version PR.
- Write only what landed. A product change gets the user-facing effect; a refactor
gets the new shape or the removed API. Nothing else.
