Skip to content

Release Checklist

Generates a scoped pre-release checklist for game builds, bugs, and store certification.

Stars
32,965
Licence
MIT
Files
1 file

What it does

When installed, the agent can produce a release-readiness checklist for a game project. It reads the project's config, milestone notes, and bug records, scans source code for TODO, FIXME and HACK comments, and then lists build, bug, and certification items scoped to the project's stage and target store. It is designed to flag what is unassessed rather than silently ticking items that cannot be verified.

Great for

  • Game developers preparing a release on PC, Steam, itch.io or consoles
  • Teams that keep milestone notes and bug records in the expected folder layout

Skip it if

  • Non-game software: the checklist is written around game platforms and certification tracks (TRC, XR, Lotcheck), so it will not fit most other projects
  • Anyone expecting it to actually run a build or submit to a store: the skill only reads files and writes a checklist, and the checklist items still need a human to verify them

Try asking

  • “/release-checklist pc”
  • “/release-checklist console”
  • “Run the release checklist for the 1.2 milestone on Steam”
Step-by-step guide: how to use Release ChecklistInstall, first run, examples, tips and FAQs

Install in 3 steps

  1. 1

    Download the skill

    The ZIP contains the 1 original files, the MIT licence and an attribution note.

    release-checklist.zip
  2. 2

    Add it to your agent

    Claude Code (all projects)

    mkdir -p ~/.claude/skills && unzip release-checklist.zip -d ~/.claude/skills/

    Claude Code / Agent SDK (this project only)

    mkdir -p .claude/skills && unzip release-checklist.zip -d .claude/skills/

    Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.

  3. 3

    Ask for the task

    No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.

Get better results

  • Set cert_tier and project.stage in project.yaml first, otherwise the checklist will ask questions or mark sections NOT ASSESSED
  • Keep bug files in production/qa/bugs/ with Severity and Status lines so the bug items can be assessed

What's inside

  • SKILL.md

Redistributed unmodified from Donchitos/Claude-Code-Game-Studios under the MIT licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.