patch-notes

Generate player-facing patch notes by aggregating internal changelog data, sprint retrospectives, balance documents, and git history. The skill maps developer language to player-friendly phrasing while preserving context and before/after values, saving the output to docs/patch-notes and production/releases.

Converting git history and developer changelogs into release documentation involves aggregating data from multiple internal sources, applying tone guidance, and using a patch-notes template if present. It maps technical changes into player-friendly communication styles.

Yes, you can produce player-facing patch notes in three styles: brief, detailed, or full. This allows you to suit different communication needs while consistently mapping developer language to player-friendly phrasing.

To map developer language to player-friendly phrasing, the skill reads multiple internal sources like changelogs and balance documents, applies tone guidance, and preserves context and before/after values where available during the phrasing translation.

Automating patch notes generation requires internal sources including production/releases/[version]/changelog.md, docs/CHANGELOG.md, sprint retrospectives, balance documents, and git history to assemble comprehensive player-facing release notes.

Yes, patch notes generation works without a custom template by applying default tone guidance to map developer language. If a patch-notes template is present, the skill will use it to structure the final output.