changelog

To auto-generate release notes from git history, the Skill reads recent commits, sprint reports, and design documents to synthesize structured internal changelogs and player-facing summaries. It parses repository tags and commit metadata to categorize entries for release tracking.

Yes, you can create separate internal and player-facing changelogs from the same git commits. The Skill produces dual output: a detailed internal changelog with categorized entries and metrics, plus a concise, player-friendly summary ready for community release.

The best way to generate game development changelogs after a sprint is to combine repository git history with production/sprints/ reports and design/gdd directories. The Skill enriches commit data with sprint reports and design documents to explain why changes were made.

Yes, generating changelogs requires read access to git history, production/sprints and design/gdd directories, and the ability to read or write docs/CHANGELOG.md. The Skill checks repository state and offers append or overwrite options with sensible defaults.

You need sprint reports and design documents to generate git changelogs because they provide contextual enrichment. While git commits show what changed, sprint reports and design docs explain why changes were made, producing more meaningful internal and player-facing release notes.

A limitation of automating changelog generation from repository history is that it depends on well-structured commit messages and available sprint documentation. Without proper context in production/sprints and design/gdd directories, the generated internal and player-facing changelogs may lack meaningful explanatory detail.