changelog

To generate a changelog from git commit history automatically, this Skill analyzes your commit logs, parses sprint data, and extracts design documents to produce categorized technical logs and release notes.

Yes, you can generate player-facing release notes from git commits and sprint data. The Skill processes development inputs and separates them into user-friendly external summaries and detailed technical logs.

Automated changelog generation categorizes git commits by parsing logs, sprint reports, and design documents to organize changes into features, improvements, bug fixes, balance adjustments, and known issues.

You do not strictly need sprint reports and design documents to generate release notes from git logs, but including them enhances the changelog by adding contextual balance adjustments and known issues.

The best way to create categorized release notes after a development sprint is to use an automated tool that reads git commits, integrates sprint data, and classifies changes into features and bug fixes.

Your git commit categories may not separate features from bug fixes because the changelog requires parsing sprint data and design documents alongside commit logs to accurately classify changes.