Generate player-facing patch notes from changelogs, git history, and QA records.
npx skills add https://github.com/dnkrow/skill --skill patch-notes-dnkrow
Please help me install this Agent Skill. Skill: patch-notes Source: https://github.com/dnkrow/skill/tree/main/claude-global/patch-notes Command: npx skills add https://github.com/dnkrow/skill --skill patch-notes-dnkrow
It turns scattered release artifacts (git history, changelogs, sprint context, and balance notes) into polished patch notes written in player-friendly language, so you do not have to manually translate developer updates.
Run patch-notes for version 1.2.0 with the brief style by asking your Claude Code agent: "/patch-notes 1.2.0 --style brief".
High-intent search queries and answers about installing and using this skill.
You can generate patch notes by running the patch-notes command with a specific version number to collect git history, changelogs, and QA records, translating them into player-facing release notes. It automatically categorizes updates into structured sections like New Content and Bug Fixes.
Translating developer changelogs into player-ready release notes is done by collecting release artifacts and applying tone detection from local documentation. This process structures updates into categories like Quality of Life and Gameplay Changes, offering brief, detailed, or full output styles.
Yes, you can write patch notes in brief, detailed, or full output styles by specifying the desired format when running the command. The generated notes are saved to both public docs and internal archive locations for release communication.
No, if no changelog data is available, the patch notes generation process conditionally blocks execution. It requires YAML-defined parameters and gathers data from git history, sprint retrospectives, balance documents, and QA bug records to function properly.
To apply a specific writing tone to automated patch notes, the process detects tone and style guidance from local documentation files. This ensures the generated release communication matches your established community management voice.
Generated patch notes are saved to docs/patch-notes/[version].md for public documentation and production/releases/[version]/patch-notes.md for internal archiving. This dual-output approach supports both player-facing and internal release communication workflows.
FrancisVargaGenerate player-facing patch notes from changelogs, git history, and QA records.
plurigridGenerate user-facing changelogs from git commit history.
wanghaishengGenerates changelogs from git commit history, sprint reports, and design documents.
imgamerGenerate player-facing patch notes from changelogs, git history, and QA records.
