changelog

Auto-generate release notes by aggregating git commits, sprint reports, and design documents into a structured changelog. The skill consolidates development history into categorized entries for both internal documentation and public communication.

Create player-facing changelogs by formatting aggregated git commits and design documents into external release notes. The skill processes development data to produce marketing-suitable summaries separated from internal technical documentation.

Yes, you can categorize bug fixes and new features automatically when generating changelogs. The skill structures entries into categories including New Features, Improvements, Bug Fixes, Balance Changes, Technical Debt, and Known Issues.

A phase-driven workflow integrates design docs by processing development phases one through five to produce verifiable changelog outputs. It aggregates design decisions alongside commit history to capture the full context of sprint progress.

You need design documents and sprint reports to generate comprehensive internal changelogs. The skill aggregates these sources with git history to consolidate engineering progress and design decisions into a single structured log.

Metrics and known issues included when automating changelog creation cover sprint progress and current limitations. The phase-driven workflow generates verifiable outputs that satisfy end-to-end requirements for both internal and player-facing documentation.