changelog-generator

# Changelog Generator Skill Converts raw git commits, a diff summary, or developer release notes into a polished changelog entry — categorised, user-facing, and following Keep a Changelog conventions. ## Required Inputs Ask for these if not provided: - **Commits or release notes** (paste `git log --oneline`, raw commit messages, or a description of what changed) - **Version number** (e.g. 2.4.0, v1.0.0-beta.2) - **Release date** (or "today") - **Audience** (developers using an API / end users of a product / internal team — affects language) - **Any breaking changes** (flag these explicitly if known) - **Previous version behaviour** (optional — paste the previous changelog entry or describe what is changing; needed for accurate "Changed" entries) - **Scope** (whole product / specific package or module — e.g. "payments SDK only", "iOS app", "all services") ## Output Format Follow [Keep a Changelog](https://keepachangelog.com) format: --- ## [X.Y.Z] — YYYY-MM-DD ### Breaking Changes ⚠️ [Only include if there are breaking changes] - **[Breaking change]:** [What changed and what it breaks] - **Migration required:** [Specific action the user must take] ### Added - [New feature or capability, written from the user's perspective] - [Another addition] ### Changed - [Changed behaviour — what it did before vs. what it does now] - [Performance improvement with measurable impact if known] ### Fixed - [Bug fixed — describe what was broken, not the fix implementation] - [Another ...