changelog

Generating release notes from git history requires parsing commit logs alongside sprint reports to produce structured markdown. This Skill aggregates technical commits and design documents to output both an internal changelog and a player-facing version.

Creating a player-facing changelog separate from internal technical notes involves parsing the same git history but tailoring the output. This Skill processes sprint reports and design documents to output concise end-user release notes alongside a detailed technical markdown changelog.

To generate changelogs from your repository, you need a Git repository with commit history, access to production/sprints/ directories, and design/gdd/ files. Providing repository context and a target version or sprint yields the two formatted markdown outputs.

Yes, you can generate markdown changelogs for projects with sprint cycles and design work. This Skill specifically parses git history, sprint reports, and game design documents to produce structured internal and player-facing release notes.

The best way to consolidate git commits and design documents into release notes is to aggregate them into a structured markdown format. This Skill parses git history and design documents to deliver a coherent narrative of changes for both engineers and end users.