Release Checklist

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 "Release Checklist" for me. The skill itself generates a pre-release checklist scoped to the project: it reads the project CLAUDE.md, the current milestone and the open bugs under production/qa/bugs/, scans the codebase for TODO/FIXME/HACK comments with an explicit files-scanned denominator, and emits build-verification, quality-gate, content, store/distribution and launch-readiness sections with a Go/No-Go verdict. Its platform argument (pc, console, mobile or all) selects only the device-requirements sections; certification items are emitted only for the resolved platform.cert_tier (none, itch, steam or console), and an unset cert tier is asked about or marked NOT ASSESSED, never silently expanded to every track. The skill itself deploys and uploads nothing: it presents the checklist and asks in plain text before writing it to production/releases/release-checklist-[version].md. It resolves the studio configuration (rigor, workflow, project.stage, cert_tier, automation) by running the template's hooks/yaml-helper.sh, outside this skill's folder. Its frontmatter pins model: sonnet. Repository: https://github.com/Donchitos/Claude-Code-Game-Studios (the skill is the whole .claude/skills/release-checklist/ 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/release-checklist/ 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 a7bd13a309e683c5a2b8a39f18df753d423d9d0b02ccf384802e3882cac4cfd5 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. Its allowed-tools list contains no AskUserQuestion: its write approval is a plain-text question in conversation. - 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 audited, read or modified. - Integrated-system reality, from the file: at use time the skill runs the template's hooks/yaml-helper.sh to resolve rigor, workflow, project.stage, cert_tier and automation, reads one section of .claude/docs/effects-map.md and .claude/docs/code-root-resolution.md, and reads my project's CLAUDE.md, milestones under production/milestones/ and bugs under production/qa/bugs/ — files that live outside this skill's folder and are absent in a standalone install, so it cannot run as designed on its own. - At use time its only persistent output is the checklist file at production/releases/release-checklist-[version].md, written only if I answer yes to its plain-text ask. The checklist's store and certification items describe steps for me and my team; the skill itself performs no deployment, upload, store submission or network call. No third-party service, account or credential is named in the file as something the skill uses. - Do not generate any checklist, do not scan any project, do not run 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 release-checklist folder into the agent's skills directory, in a folder named exactly "release-checklist", keeping its 1 file in their original relative layout (SKILL.md at its root). 4. Verify with no network calls: frontmatter valid (name: release-checklist), 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 template's production/ files), that it deploys and uploads nothing itself, and that it writes its checklist only after its plain-text ask). 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.