changelog

Generate changelog entries by parsing a git tag or sprint date range to extract commits, then combining that history with sprint reports and design documents to produce structured patch notes. The output categorizes changes into features, improvements, bug fixes, and balance changes.

Yes, this process creates both implementation-focused internal changelogs and community-ready player-facing patch notes from the same release data. It uses git commits alongside game design documents to ensure the community messaging accurately reflects the underlying development activity.

Categorize git commits by parsing the commit history within a version range and classifying entries into New Features, Improvements, Bug Fixes, Balance Changes, Known Issues, and Miscellaneous. It also tracks a metric for commits lacking task references to ensure traceability.

Automate patch notes by running a generation process against a specific sprint number or version tag, which reads the relevant git range and sprint documentation. It outputs categorized release communication and offers to save the formatted results directly to your changelog file.

Game design documents are not strictly required but are used as supporting context to explain why changes occurred. Combining git tags and commit history with sprint reports and design documentation provides accurate feature and balance messaging for both internal logs and player announcements.