What problem does it solve? Writing release changelogs from raw git history is tedious, and the result is often either too technical for managers or too vague for developers. This Skill turns commit history into one unified changelog that the whole company can read, formatted for direct pasting into Slack. ## Core Features & Use Cases - Unified audience writing: Produces a single changelog in plain language that managers understand while keeping the detail developers need, with PR links on every line. - Flexible commit ranges: Defaults to unreleased changes (main vs develop) and supports date ranges like "today", "yesterday", "last week", or explicit git ranges such as v2.0.0..HEAD. - Slack mrkdwn output: Formats output in Slack composer syntax (bold, bullets, links) inside a code block for clean copy-paste, with an optional GitHub-flavored Markdown mode. - Use Case: Before a release announcement, run /changelog to get a Slovak-language summary of everything merged since the last release, grouped into sections like Shopping experience and Speed, ready to paste into the company Slack channel. ## Quick Start Ask the assistant to run /changelog to generate a Slack-ready changelog of unreleased changes from the current repository.