Changelog from Commits (Live)
Users don't read commit messages, and they shouldn't have to. In Claude Cowork this skill reads the real commit range and turns it into a changelog written for the people who use the software — grouped, deduped, and translated from "refactor: extract helper" into what actually changed for them.
What This Skill Produces
- The changelog — grouped into Added / Changed / Fixed / Breaking, each entry written as user-facing benefit, not commit-speak
- The breaking-change callout — migrations and removals pulled to the top with what to do
- A changelog artifact — Keep-a-Changelog style, ready to paste into
CHANGELOG.md or a release
Required Inputs
Ask for these if not provided:
- The range — from tag/ref to tag/ref (default: last tag → HEAD), and the repo
- The audience — end users, API consumers, or developers — translation depth follows
- Version & date — the release number and date for the heading
Framework: Commits → Changelog
- Group by impact — Added / Changed / Fixed / Breaking; drop internal-only churn (chore/ci/refactor) unless it changes behaviour.
- Translate — every entry says what the user can now do or no longer suffers, not the implementation.
- Dedupe & merge — many commits behind one feature become one line.
- Breaking first — removals, renames, and migrations lead, with the upgrade step.
- Credit & links — PR numbers/authors where it helps.
Execution (Cowork)
- Read the range — via the GitHub connector, list commits (and merged PRs) between the two refs, with messages, PR titles, and labels.
- Classify — map each to Added/Changed/Fixed/Breaking; set aside pure-internal churn; detect breaking changes from
!/BREAKING CHANGE/removed-public-API signals.
- Translate & merge — collapse the commits behind each user-facing change into one benefit-led line; keep PR references.
- Order — breaking first, then Added, Changed, Fixed.
- Emit the artifact — the changelog block; offer to prepend it to
CHANGELOG.md or attach to a release, only on request.
Guardrails: include only changes actually present in the range — never invent a feature; base "breaking" on real signals, not guesses; don't overstate impact; if the connector is unauthorised, work from a pasted git log and say the range couldn't be read live.
Output Format
A Changelog block:
## [version] — date
### ⚠ Breaking
- what changed → what to do (#PR)
### Added
- user-facing capability (#PR)
### Changed
- what's different now (#PR)
### Fixed
- the problem that's gone (#PR)
Quality Checks
Anti-Patterns
- Pasting raw commit messages as the changelog.
- Inventing a feature not in the range to round it out.
- Burying a breaking change in the middle of "Changed".
- Listing every
chore:/refactor: that users never see.
Example Trigger Phrases
- "Write the changelog since the last tag in Cowork."
- "Draft release notes from my commits for v2.0."
- "What changed for users between v1.4 and HEAD?"
- "Summarise this commit range as a human changelog."
1---2name: changelog-from-commits3description: "Write a human changelog from the REAL commit history — read the actual commit range via the GitHub connector, not a template."4metadata:5 source: https://skillmd.com/skills/slipcast-dev/changelog-from-commits6---78# Changelog from Commits (Live)910Users don't read commit messages, and they shouldn't have to. In Claude Cowork this skill reads the *real* commit range and turns it into a changelog written for the people who use the software — grouped, deduped, and translated from "refactor: extract helper" into what actually changed for them.1112## What This Skill Produces1314- **The changelog** — grouped into Added / Changed / Fixed / Breaking, each entry written as user-facing benefit, not commit-speak15- **The breaking-change callout** — migrations and removals pulled to the top with what to do16- **A changelog artifact** — Keep-a-Changelog style, ready to paste into `CHANGELOG.md` or a release1718## Required Inputs1920Ask for these if not provided:21- **The range** — from tag/ref to tag/ref (default: last tag → HEAD), and the repo22- **The audience** — end users, API consumers, or developers — translation depth follows23- **Version & date** — the release number and date for the heading2425## Framework: Commits → Changelog26271. **Group by impact** — Added / Changed / Fixed / Breaking; drop internal-only churn (chore/ci/refactor) unless it changes behaviour.282. **Translate** — every entry says what the *user* can now do or no longer suffers, not the implementation.293. **Dedupe & merge** — many commits behind one feature become one line.304. **Breaking first** — removals, renames, and migrations lead, with the upgrade step.315. **Credit & links** — PR numbers/authors where it helps.3233## Execution (Cowork)34351. **Read the range** — via the GitHub connector, list commits (and merged PRs) between the two refs, with messages, PR titles, and labels.362. **Classify** — map each to Added/Changed/Fixed/Breaking; set aside pure-internal churn; detect breaking changes from `!`/`BREAKING CHANGE`/removed-public-API signals.373. **Translate & merge** — collapse the commits behind each user-facing change into one benefit-led line; keep PR references.384. **Order** — breaking first, then Added, Changed, Fixed.395. **Emit the artifact** — the changelog block; offer to prepend it to `CHANGELOG.md` or attach to a release, only on request.4041Guardrails: include only changes actually present in the range — never invent a feature; base "breaking" on real signals, not guesses; don't overstate impact; if the connector is unauthorised, work from a pasted `git log` and say the range couldn't be read live.4243## Output Format4445A **Changelog** block:4647```48## [version] — date4950### ⚠ Breaking51- what changed → what to do (#PR)5253### Added54- user-facing capability (#PR)5556### Changed57- what's different now (#PR)5859### Fixed60- the problem that's gone (#PR)61```6263## Quality Checks64- [ ] Every entry maps to a real commit/PR in the range65- [ ] Entries read as user benefit, not commit messages66- [ ] Breaking changes lead and include the migration step67- [ ] Internal-only churn was excluded (unless it changed behaviour)68- [ ] Multiple commits behind one feature are a single line6970## Anti-Patterns71- **Pasting raw commit messages** as the changelog.72- **Inventing a feature** not in the range to round it out.73- **Burying a breaking change** in the middle of "Changed".74- **Listing every `chore:`/`refactor:`** that users never see.7576## Example Trigger Phrases77- "Write the changelog since the last tag in Cowork."78- "Draft release notes from my commits for v2.0."79- "What changed for users between v1.4 and HEAD?"80- "Summarise this commit range as a human changelog."