changelog

Generate release notes by selecting a git commit range from tags or sprint date windows, applying categorization heuristics to commit messages, and outputting categorized markdown. This transforms scattered history into structured patch notes.

Yes, this process creates both internal and player-facing changelogs from the same git history. The player-facing version uses accessible language that avoids implementation details, while the internal version retains technical specifics.

Categorize commits by applying heuristics based on commit messages and task references. This groups git history into distinct release note categories like features, improvements, bug fixes, and balance changes automatically.

Generating a changelog requires git availability checks to access commit history. You need a git repository with tagged releases or date windows to define the commit range for sprint-scoped or tag-scoped summaries.

The best way to document game development patch notes is transforming git commits, sprint reports, and design documents into categorized release notes. This grounds the summary in commit intent and design rationale.

Yes, you can write sprint-scoped or tag-scoped changelogs directly to docs/CHANGELOG.md. The final output is suitable markdown formatted for saving directly into your documentation directory.