slack-changeloglisted

Turns what changed in a release into a Slack changelog a non-technical audience can read: filtered to what they would actually notice, one bullet per idea, plain language, no code vocabulary. Works out the scope itself across however many repositories sit in the working directory (a project can span several independent repos released together), separates what is visible to someone outside engineering from what isn't, groups the visible part by functional theme rather than by repo, picks an emoji per idea from a reference table, and closes on a single question round to adjust theme, bullets, closing line or target channel before handing over the final text. It never posts on its own. Use it when someone wants to announce a release to people outside engineering: "écris le changelog Slack pour cette release", "prépare le message pour annoncer les dernières nouveautés", "on doit poster ce qui a changé pour les équipes business", "draft the Slack update for this release", "what should we tell the rest of the compa
Malo-T/claude-toolbelt · ★ 2 · Code & Development · score 66

Install: claude install-skill Malo-T/claude-toolbelt

# Slack Changelog Turn a release into a message the rest of the company can read, not a changelog for engineers. The audience is anyone who doesn't read diffs: support, sales, ops, whoever sits in the channel. They need to know what changed for them, in plain language. Not how it was built. The deliverable is a ready-to-post Slack message: a fixed template, a handful of bullets, one emoji each, an optional closing line, always the channel-wide mention. Not the commit log with nicer punctuation. A translation of it, filtered down to what someone outside engineering would actually notice. Two failure modes to avoid. A technical changelog with emoji stapled on: a bullet that names a class, a status code, or a function has failed, however it's formatted. And a post sent without asking: the draft stays a draft until the user has seen it and said so. ## Invocation ``` /slack-changelog [optional scope] ``` Examples: - `/slack-changelog` - `/slack-changelog v2.4.0..HEAD` - "écris le changelog Slack pour cette release" - "prépare le message pour annoncer les dernières nouveautés côté connexion" - "draft the Slack update for what shipped this week" ## Step 1 — Resolve the scope Know exactly which changes you're translating before you start drafting. **If the working directory holds a single repository**, resolve the range the way `branch-recap` does: an explicit range the user named, otherwise the latest tag through `HEAD` (the usual release cut point), falling back to the mer