patch-notes

Name: patch-notes
Availability: InStock
Author: scomofo

Generate player-facing patch notes from git history and changelog sources.

Updated Mar 28, 2026

Search Tags:#release management #template generation #git history #patch notes #change translation #community communication #tone guidance

Ready to run

npx skills add https://github.com/scomofo/dragon-forge --skill patch-notes-scomofo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: patch-notes
Source: https://github.com/scomofo/dragon-forge/tree/main/.agents/skills/patch-notes
Command: npx skills add https://github.com/scomofo/dragon-forge --skill patch-notes-scomofo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates the manual, developer-to-player translation work of turning internal change logs and sprint evidence into clear patch notes players can actually read.

Core Features & Use Cases

Versioned patch note generation: Creates patch notes for a specific release version using internal changelog files, docs entries, git history, sprint retrospectives, balance docs, and QA bug-fix records.
Tone and template aware output: Detects writing voice guidance and optionally applies a discovered patch-notes template to structure the final result.
Actionable, player-focused categorization: Organizes changes into New Content, Gameplay Changes, Quality of Life, Bug Fixes, Performance, and Known Issues while converting internal jargon into player language.
Release-archive saving: Produces a draft and then, when approved, writes the notes to both the public patch-notes path and the internal archive.

Quick Start

Generate patch notes for version 1.2.0 using the detailed style: /patch-notes 1.2.0 --style detailed

Frequently Asked Questions about patch-notes

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I generate patch notes from git history and internal changelogs?▼

Generate patch notes by loading internal changelog files, sprint retrospectives, balance docs, and QA records for a specific release version, falling back to git history when needed to produce player-ready output.

Can I automatically categorize game changes into highlights and bug fixes?▼

Yes, automatically categorize game changes into structured sections like New Content, Gameplay Changes, Quality of Life, Bug Fixes, Performance, and Known Issues by applying detected tone guidance and optional templates.

What is the best way to translate internal developer jargon into player-facing patch notes?▼

Translate internal developer jargon into player-facing patch notes by processing internal changelog sources and applying tone guidance detection to convert technical change records into readable language.

Does patch note generation block execution if no changelog data exists?▼

Yes, execution blocks when no changelog data exists for the requested version, requiring relevant changelog paths or accessible git history before generating the player-facing patch notes.

How do I save approved patch notes to internal archives and public destinations?▼

Save approved patch notes by writing the final output to both the configured public patch-notes path and the internal archive destination upon explicit approval of the generated draft.

Can I use a specific template to structure sprint retrospective data for a game release?▼

Yes, apply a discovered patch-notes template to structure sprint retrospective data, organizing changes into predefined categories while applying tone guidance for player-ready communication.