patch-notes

Generate player-facing patch notes by aggregating internal changelogs, sprint retrospectives, and git history into accessible summaries. The tool processes data from docs/CHANGELOG.md and design/balance docs to produce coherent notes that improve release communication and player understanding.

Format release notes for different audiences using brief, detailed, or full output styles. The tool applies tone and template guidance to your aggregated changelog data, allowing you to scale the depth of release communication from quick summaries to comprehensive feature launch breakdowns.

Create patch notes for a specific version by applying the tool to your release cycle context. It aggregates data from production/releases/[version]/changelog.md and sprint docs to describe changes, gracefully handling missing data or blockers to ensure your release communication proceeds smoothly.

Sprint retrospectives and balance docs are translated into patch notes through data aggregation and tone detection. The tool extracts relevant changes from production/sprints and design/balance docs, then applies player-facing tone guidance to rewrite internal development context into clear, accessible summaries.

When the changelog is missing data, the patch notes generation handles the gaps gracefully. Instead of failing, it aggregates whatever information is available from existing git history and sprint contexts, ensuring you still get a functional draft for your release communication.

The tool works for both hotfixes and full version releases. It aggregates data from your changelog and git history to produce transparent summaries, making it ideal for any release cycle where players need accessible updates about recent changes.