Patch Notes

Before you start: read this whole install prompt, tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead before you do anything else. Prerequisites — INTEGRATED SYSTEM FIRST: this skill is one piece of the complete "Claude Code Game Studios" template (49 agents, 74 skills, studio templates and a studio CLAUDE.md, per the repository README). Each skill assumes that template is installed, with its conventions, its project.yaml / project.local.yaml configuration, its .claude/docs/ mode documents, its hooks (for example hooks/yaml-helper.sh, outside this skill's folder) and its .claude/scripts/ helpers. Installing this listing alone copies only this skill's folder, without the rest of the system: the skill may reference template agents, files, hooks or scripts that are absent outside the full template, and it may not run as designed on its own. No account, no key and no payment are needed to copy the files, and nothing is run during installation. Install "Patch Notes" for me. It writes player-facing patch notes for a version from the project's own history. Before reading any history it runs a provenance check: it samples git log, classifies every commit as Game, Framework/maintenance or Unclear, uses only Game commits, and stops with a BLOCKED verdict if none of them belong to this game — framework commits must never be rendered as player copy. It then reads the internal changelog at production/releases/[version]/changelog.md or docs/CHANGELOG.md, git log between release tags, sprint retrospectives and balance documents, detects a tone guide and a patch-notes template in the project when they exist, and translates developer language into player language in brief, detailed or full style. It asks before writing both docs/patch-notes/[version].md and an archive copy at production/releases/[version]/patch-notes.md. The notes are public player-facing copy; publishing them is your own later step. Repository: https://github.com/Donchitos/Claude-Code-Game-Studios (the skill is the whole .claude/skills/patch-notes/ folder at the pinned commit: 1 file in total) Pinned version: install the code at commit 05ad7c8a5b8aa2aa86bbd3439ae7cf7295cac418 exactly. Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Clone https://github.com/Donchitos/Claude-Code-Game-Studios into a temporary folder, check out commit 05ad7c8a5b8aa2aa86bbd3439ae7cf7295cac418, and copy the .claude/skills/patch-notes/ folder from that checkout. Then compare every file in the folder with the fingerprints recorded for this listing on 2026-10-22: [FINGERPRINTS] - SKILL.md: SHA-256 41e7a4b4b1d5536dd2957ffa048a80391ddcf2c6cf8eac169b05962d66c5f0e7 If a file does not match, it changed since the listing was prepared: do not install it yet, tell me what you found and let me decide. 2. Read SKILL.md in full, and tell me in plain words: what the skill does when used, what it connects to, whether it reads or sends any personal information or credentials, and anything that seems unusual. Stop on any red flag and tell me before going further. Confirm these points from the files: - The skill folder holds 1 file: SKILL.md only. Nothing in the folder is a program; it is instructions the agent follows at use time. - Nothing is sent anywhere during installation itself; the only download at install time is the skill folder from GitHub at the pinned commit, and no project of mine is read or modified, and no git command is run. - Integrated-system reality, from the file: at use time the skill resolves its automation mode by running the template's hooks/yaml-helper.sh (key automation) and is explicitly allowed to run git log in my project; it reads production/releases/, docs/CHANGELOG.md, production/sprints/, design/balance/, the tone and template files under .claude/docs/, docs/ and design/community/ — project and template files outside this skill's folder, and the provenance check exists precisely because the game repo and the framework repo are the same repository in this template. - At use time it writes only after asking, and writes two files: docs/patch-notes/[version].md and the archive copy production/releases/[version]/patch-notes.md. The output is player-facing public copy meant to be posted publicly later — that posting is my own step, and the skill names no service, account or credential and sends nothing itself. - Do not generate any patch notes, do not run git log or any template hook, and do not use the skill in any way during this install: using it is a separate step that only starts when I ask for it later. 3. When I say "yes, install", install it as a skill: copy the whole patch-notes folder into the agent's skills directory, in a folder named exactly "patch-notes", keeping its 1 file in their original relative layout (SKILL.md at its root). 4. Verify with no network calls: frontmatter valid (name: patch-notes), the 1 file in place with matching fingerprints. Do not run anything from the folder and do not use the skill to verify. 5. Report what was installed, where, and what I still need to do myself (for example: that it belongs to the full Claude Code Game Studios template and may not run standalone (it resolves its settings through the template's yaml-helper hook and reads the project's changelogs, git history and template tone files), and that it writes both patch-notes files only after asking). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.