Iron Law: Never generate a changelog without reading actual git history or diff; always base entries on verified commits, not assumptions.

Changelog Generator Skill

Transform git commit history into polished, user-friendly changelogs. Works with any tech stack by auto-detecting the project structure.

High-Level Process

1. Detect project structure - Scan repo for platform markers (Java, Node, Python, Angular, Flutter, etc.) and build a platform label map
2. Determine commit range - Use tags, dates, or commit count. Ask user if unclear
3. Extract commits - Pull structured log: git log "$LAST_TAG"..HEAD --pretty=format:"%h|%ai|%an|%s" --no-merges
4. Categorize - Map conventional commit prefixes to user-facing categories (feat -> New Features, fix -> Bug Fixes, perf -> Performance). Skip refactor/test/chore/ci/build/style
5. Rewrite - Translate technical commits to user-friendly language. Lead with user benefit, strip jargon
6. Assemble - Format changelog for the target destination
7. Output - Write to CHANGELOG.md, GitHub Release, App Store, Slack, or internal format

For detailed step-by-step workflow (project detection scripts, commit parsing, categorization table, rewriting rules, assembly format) -> Read reference/changelog-workflow.md

For output format examples (App Store, Keep a Changelog, internal/technical, Slack/email) -> Read reference/changelog-workflow.md