changelog

Automating changelog generation from git commits and sprint reports requires parsing version tags, aggregating data from the repository's git CLI and sprint directory, and categorizing changes into formatted markdown files. This skill produces both internal and player-facing changelogs automatically.

Categorizing release notes from git commits involves parsing commit history, sprint reports, and design documents to automatically sort changes into features, improvements, bugs, balance tweaks, known issues, and miscellaneous sections for formatted markdown output.

Yes, generating internal and player-facing release notes from a single version tag is possible by applying the tag or sprint number as the scope, aggregating git and design document data, and producing categorized markdown files tailored for each audience.

Access to the repository's git CLI, the production or sprints directory, and design or game design document files is required to aggregate commit history and sprint data for generating categorized changelogs and release metrics.

Generated release notes integrate with existing workflows by supporting commands like patch-notes and release-checklist, allowing categorized changelog markdown files to feed directly into downstream software release processes.