Changelog Generator Skill

Generate changelogs that strictly follow the Keep a Changelog 1.1.0 format.

This skill works from commit subjects only — no diffs, no --stat, no file inspection. This keeps it fast and honest: the quality of the output reflects the quality of the commit messages.

Step 0 — Ask for audience context before doing anything

Before running any git commands, ask the user one question:

"Who's the primary audience for this changelog — end users, developers/API consumers, or internal team/ops?"

This changes the language significantly:

• End users: plain English, no technical terms, focus on visible behaviour ("You can now export reports as PDF")
• Developers: can reference APIs, modules, config changes ("Added exportReport(format) to the SDK")
• Internal/ops: can mention infra, deploy steps, env var changes ("Requires REDIS_URL env var on deploy")

If the user is in a hurry and says skip it, default to developers.