Kiss changelog
KiSYSTEM - measure twice, cut once. A Claude Code skill bundle that keeps AI-written code clean, modular, and human-readable, enforced from the base of a project.
npx -y skills add Pr1m4lc0d3/KiSYSTEM --skill kiss-changelogAssembled 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.
What its author says it does
Copied from the file, not written here
Use after a change lands — a feature, a fix, or any behavior change — to record what changed and why, so humans and future-you can follow the project's evolution without reading the diff. Use before declaring a unit of work done, not in a batch at the end.
SKILL.md
2.0 KB, as published. Nobody here has run it
KISS — Changelog
A changelog is the project explaining its own history. Per-unit synopses keep a file legible
(kiss-readable); the changelog keeps the project legible over time. Write the entry when the cut
lands — not "later," because later it's reconstructed from memory and half of it is wrong.
The ritual — when a cut lands
Before you call a unit of work done, add an entry:
- What changed — one line.
- Why — the reason, not just the mechanic.
- Where — the files touched.
Group under Added / Changed / Fixed (the Keep a Changelog convention).
Two tiers — scale to the project
- Simple project: one
CHANGELOG.md, entries under## [Unreleased]. - Shipping product: an internal log (every change, never trimmed, never ships) plus a
public log (a user-facing summary, per release). At release, move
[Unreleased]into a versioned block and distill the public summary from it.
Entry quality
- What and why, not just what. "Fixed double-count" < "Fixed double-count — totals summed the draft and final rows because both carried the same id."
- Keep noise out of the public log (whitespace, internal renames).
- Never let it drift behind the code. A changelog that lies is worse than none — update it as part of the cut, not as an afterthought.
Why it's a measure-twice discipline
Writing the entry forces you to state, in one line, what you actually changed and why. That's a
final measurement: if you can't summarize the cut in a sentence, you probably did more than you were
asked to — go back and check the blast radius (kiss-blast-radius). The changelog isn't just
record-keeping; it's the receipt that proves the cut was intentional and scoped.
Gives 0 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 formatin 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.mdin 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
- add an entry before calling work done
- state what changed and why
- list the files touched
- place unreleased entries under an Unreleased heading
- write entries as part of the cut
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.