patch-notes

Convert internal changelogs and git history into player-facing patch notes.

14|1|Updated Apr 12, 2026

Search Tags:#changelog #templates #release-notes #patch-notes #sprint-data #tone-detection #player-communications

Ready to run

npx skills add https://github.com/Euraika-Labs/Codex-Code-Game-Studios --skill patch-notes-euraika-labs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: patch-notes
Source: https://github.com/Euraika-Labs/Codex-Code-Game-Studios/tree/main/.agents/skills/patch-notes
Command: npx skills add https://github.com/Euraika-Labs/Codex-Code-Game-Studios --skill patch-notes-euraika-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Patch notes are often technical and opaque; this Skill converts internal development updates into clear, player-facing communications.

Core Features & Use Cases

Automatically aggregate changelogs from production/releases, docs/CHANGELOG.md, git history, sprint retrospectives, and balance docs.
Detect tone and apply a player-friendly voice using a built-in template system to produce Brief, Detailed, or Full style notes.
Generate release notes for versions across patches, hotfixes, and major updates, with optional developer commentary.

Quick Start

Generate patch notes for version 1.2.0 using the internal changelog and sprint data.

Frequently Asked Questions about patch-notes

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

FAQPage Schema

How do I generate player-facing patch notes from git logs and internal changelogs?▼

Generate player-facing patch notes by automatically aggregating internal changelogs, git history, and sprint data into readable communications. The system detects tone and applies templates to convert technical development updates into clear release notes for your players.

What is the best way to convert technical sprint retrospectives into release notes?▼

Converting sprint retrospectives into release notes involves aggregating internal balance docs and sprint files, then applying tone detection to create player-friendly communications. You can output the generated notes in Brief, Detailed, or Full styles depending on your audience needs.

Can I include developer commentary when converting changelogs into patch notes?▼

Yes, you can include optional developer commentary when generating patch notes from internal changelogs. This feature allows you to add contextual insights directly within the Brief, Detailed, or Full style release notes created from your git history and design documents.

Does this patch note generation approach support hotfixes and major game updates?▼

Patch note generation supports hotfixes, patches, and major updates by aggregating data from production releases and design docs. It automatically detects the appropriate tone and applies player-friendly templates to communicate changes across all release types.

What formats and styles of release notes can I create from internal balance docs?▼

You can create Brief, Detailed, or Full style release notes from internal balance docs and design notes. The system uses a built-in template system with tone detection to ensure the output maintains a player-friendly voice across different release formats.

Why are my technical changelogs opaque to players and how do I fix it?▼

Technical changelogs are often opaque because they use developer-specific language; you can fix this by using tone detection to convert them into player-facing patch notes. The system automatically translates internal git logs and sprint data into clear, player-friendly communications.