patch-notes

To generate patch notes from git log and changelog data, the skill synthesizes release history, sprint context, and docs entries into categorized, player-facing updates. It translates developer phrasing into understandable impact statements grouped by category.

Converting internal developer changelogs into community-friendly release communication requires translating technical changes into player-language impact statements. The skill detects community tone preferences and applies templates to produce publishable updates across brief, detailed, or full formats.

Yes, you can include before and after balance values when generating gameplay patch notes. The skill explicitly supports translating balance changes into player-facing updates by providing before/after values alongside categorized gameplay modifications.

The best way to format patch notes for features, fixes, and quality of life improvements is categorizing them into distinct publishable update groups. The skill outputs brief, detailed, or full formats that group fixes by category and validate version context.

Patch note generation works without a predefined template by detecting community tone preferences and falling back to built-in formats. If no template is provided, it automatically follows brief, detailed, or full output styles based on available release data.

If changelog data is missing when creating release notes, the skill falls back to locating alternative release data sources. It validates that version context exists before producing categorized output, ensuring generated patch notes remain accurate and publishable.