← ClaudeAtlas

game-releaselisted

Use when a Unity 6 mobile game generated from the cmpose template is about to go to Google Play or the App Store, when asked whether the game is ready to ship, for a store release checklist, or after launch for a post-mortem.
whinstudio/skills · ★ 0 · AI & Automation · score 63
Install: claude install-skill whinstudio/skills
# Game release Checks that a game is ready for the stores by reading its real files and running exact commands, then writes a verdict. It writes only `qa/release-<date>.md`; row 6 also writes `Builds/` and may touch `Library/`. The post-mortem is a separate mode: [post-mortem](references/post-mortem.md). Every row below is one of two kinds: - **Checked**: a command or file read in this project. The result is `PASS`, `FAIL` or `NOT RUN`. Rows 12 and 13 only state a value and have no failure: their result is `stated`. A row that does not apply to this game is `n/a`; `WARN` is a stated concern that is not a failure. - **Needs the owner**: a store console, a real device or legal text. It is `NOT ASSESSED` unless the user confirms it in this conversation; then it is `CONFIRMED` and says who confirmed. Do not mark a row `PASS` from memory, from the README, or because a similar row passed. ## Verdict First match wins: 1. `NOT READY`: any checked row is `FAIL`. 2. `NOT ASSESSED`: any row is `NOT RUN`, or an owner row is unconfirmed. Name each one. 3. `READY`: every row is `PASS`, `PASS (debug-signed)`, `WARN`, `stated`, `n/a` or `CONFIRMED`. `WARN`, `stated` and `n/a` never change the verdict. (`PASS (debug-signed)` counts as `PASS`; row 5 fails in that case, so rule 1 applies first.) ## 0. Project The project is the current directory unless the request gives a path; `cd` into it first, because the commands below use relative paths. `Assets/` and `ProjectSettings/` mu