Changelog

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 "Changelog" for me. It is the Game Studios changelog generator. Two history blocks (git log --oneline -30 and the recent tags) are auto-resolved into the skill before its body runs; a provenance check then classifies each injected commit as Game, Framework/maintenance or Unclear, uses only the Game ones, and stops with BLOCKED when none of them belong to the game — the stated reason is that framework commits rendered as player copy would be fluent, plausible and false. It then reads the commits since the last tag (bounded to the last 100 when no tag exists), the sprint reports and the GDD sections for the period, categorises every change (new features, improvements, bug fixes, balance, technical debt — internal changelog only — known issues, miscellaneous), counts commits without a task reference, presents an internal changelog and a player-facing one (no code references, file paths or developer names), and writes docs/CHANGELOG.md only on the user's choice: append, overwrite, or not at all. Repository: https://github.com/Donchitos/Claude-Code-Game-Studios (the skill is the whole .claude/skills/changelog/ folder at the pinned commit: 1 files 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/changelog/ 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 e8ab97b0b07e7cfef09d00b1d273ec7b926fba26c567853a03843243e25874f2 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 only: SKILL.md (10275 characters of instructions in a single file; there are no companion files in its folder). Nothing in the folder is run during installation; companion files are instructions/references the skill reads at use time, copied as-is. - 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. - Integrated-system reality, from the files: at use time the skill resolves the automation mode by running the template's hooks/yaml-helper.sh, follows the template's .claude/docs/automation-modes.md, and runs git log, git tag and git rev-parse in my project through Bash — its recent-history blocks are resolved from my repository's git history before the body runs. Its provenance rule is kept identical to the template's /patch-notes skill on purpose. These are template conventions and my own local git data; the skill reads my project's sprint reports and GDDs locally. - At use time it writes only on my explicit choice (append or overwrite) and only one file in my own project: docs/CHANGELOG.md, holding the internal changelog; the player-facing version is presented for review and community posting stays mine to do. No account, key, payment or third-party service is named in the files I read; its git reads are local. - Do not generate any changelog, do not run git 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 changelog folder into the agent's skills directory, in a folder named exactly "changelog", keeping its 1 files in their original relative layout (SKILL.md at its root). 4. Verify with no network calls: frontmatter valid (name: changelog), the 1 files 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 mode through the template's yaml-helper hook), and that inside the template it builds changelogs from my local git history and writes docs/CHANGELOG.md only on my choice). 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.