changelog

You can auto-generate changelogs by consolidating Git commits, sprint reports, and design documents into structured outputs. The skill reads sprint metadata and design docs to contextualize changes, producing both internal technical logs and player-facing release notes.

Yes, generating both internal and player-facing release notes from the same sprint data is supported. The internal changelog includes technical commits and owners, while the player-facing version translates changes into friendly community documentation.

To organize design documents and sprint reports for automated changelog generation, place sprint reports in the production/sprints directory and design documents in the design/gdd directory. The skill reads these paths to contextualize the generated changelog scope.

An automatically generated game development changelog includes sections for features, improvements, bug fixes, balance changes, and known issues. It also appends metadata detailing the specific commits and owners responsible for the changes.

Yes, providing a target version or sprint number is required to determine the scope of the changelog. This version or sprint metadata dictates which git commits and design documents are consolidated into the final output.