release-checklist

Generate a pre-release verification checklist for platform-specific release workflows.

Updated Apr 22, 2026
One-click install
npx skills add https://github.com/brand6/Claude-Code-Game-Studios-zh-auto --skill release-checklist-brand6
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-checklist
Source: https://github.com/brand6/Claude-Code-Game-Studios-zh-auto/tree/main/.claude/skills/release-checklist
Command: npx skills add https://github.com/brand6/Claude-Code-Game-Studios-zh-auto --skill release-checklist-brand6

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates a comprehensive pre-release verification checklist that ensures build validation, authentication readiness, storefront metadata, and overall release readiness are addressed before shipping.

Core Features & Use Cases

  • Stage-driven checklist generation covering code health, QA gates, content validation, and publishing readiness.
  • Platform-aware outputs for pc, console, mobile, or all workflows.
  • Use Case: before shipping a new version, generate a checklist to verify licensing, metadata, and distribution readiness.

Quick Start

Invoke the /release-checklist command with a target platform flag to generate the pre-release checklist (e.g., /release-checklist platform=pc).

Frequently Asked Questions about release-checklist

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a pre-release verification checklist for a game build?

A pre-release checklist ensures build validation, authentication readiness, and storefront metadata are verified before shipping. It guides teams through stage-driven checks across code health, content validation, and distribution readiness.

Can I create a release readiness checklist for specific platforms like console or mobile?

Yes, release checklists can be generated for pc, console, mobile, or all-platform workflows. You specify the target platform when invoking the command to receive validation steps tailored to that distribution channel.

How do I verify storefront metadata and licensing before publishing a new release?

Verifying storefront metadata and licensing before publishing involves running a pre-release checklist that includes publishing readiness validation. It confirms metadata accuracy and licensing compliance before distribution.

Does the release checklist generation require any specific project configuration files?

Release checklist generation requires a CLAUDE.md file to define project scope, milestones, and release criteria. Reading this context allows the checklist to conform to specific project validation requirements.

What is the best way to ensure QA gates and build validation are completed before a release?

Using a stage-driven pre-release checklist is the best way to ensure QA gates and build validation are completed. It systematically covers code health and content validation to confirm release readiness.