changeloglisted

Writes the CHANGELOG.md entry for the work just done, in the voice of somebody telling a k0 user what they will notice — and brings README.md, docs/database.md and docs/testing.md up to date in the same pass. Use this skill whenever the user says they want to commit, push or release, in whatever words and whatever language they say it — "commit this", "push it", "cut a release", "committa", "pusha", "fai una release". It also closes [Unreleased] into a numbered version, bumps package.json and tags, stopping to ask once before the push that publishes. Do not use it when the user is only asking what changed, when the change touches nothing but .claude/, or when it is a repair to the changelog itself.
alessio-ragni/k0-board · ★ 1 · Data & Documents · score 74

Install: claude install-skill alessio-ragni/k0-board

# The changelog `CHANGELOG.md` is the only place a person who does not read code finds out what happened to k0. It is not a list of commits and it is not for the person who wrote them. Somebody who installed k0 last month opens it to answer one question: **what is different for me now?** Everything below exists to keep that answer readable. This skill is not something the user invokes. It runs because they said they wanted to commit, push or release, and it runs *before* that, so the entry is part of the same commit as the work. ## When it does not run - The user is asking what changed, or reading a diff. Nothing is imminent. - The change touches only `.claude/` — tooling for whoever is working on k0, not k0. - It is a repair to the changelog itself. - The work is half finished. An entry describes something that is done. ## What to do, in this order **1 · Look at the work, not at the commit messages.** ``` git status --porcelain git diff --stat git log origin/main..HEAD --oneline --no-merges git branch --show-current date +%F ``` Then read enough of the actual diff to be able to answer the question at the top of this file. A commit message says `fix: guard the path join`; that is not an answer. **2 · Bring the documentation up to date first, in the same change.** The entry is written last because writing it is what proves the work is finished, and the documentation is part of the work: - `README.md` — anything a user can see belongs in the manual, and anything tha