release-checklist

Generate a pre-release validation checklist from project context and codebase signals.

Updated Apr 25, 2026
One-click install
npx skills add https://github.com/easonlao/jiazi-game --skill release-checklist-easonlao
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-checklist
Source: https://github.com/easonlao/jiazi-game/tree/main/.claude/skills/release-checklist
Command: npx skills add https://github.com/easonlao/jiazi-game --skill release-checklist-easonlao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents last-minute release surprises by turning scattered validation steps into a single, comprehensive pre-release checklist you can verify before launch.

Core Features & Use Cases

  • Pre-release validation coverage: Creates a release checklist spanning build verification, quality gates, and content completeness.
  • Platform-aware requirements: Adds PC, console, or mobile certification/launch items based on the target platform argument.
  • Release artifact generation: Optionally writes the generated checklist to production/releases/release-checklist-[version].md and can direct you to further gate/sign-off skills.

Quick Start

Run /release-checklist with the platform argument you’re targeting to generate a readiness checklist and then choose whether to save it to the releases folder.

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 validation checklist for a game launch?

A pre-release validation checklist scans project context, milestone state, and codebase signals like TODO/FIXME/HACK to produce comprehensive build verification and launch readiness items for your specified target platform.

What is the best way to track production milestones and code blockers before a store release?

Tracking production milestones and code blockers before a store release involves scanning milestone files under production/milestones and summarizing TODO/FIXME/HACK counts to evaluate platform readiness and certify launch quality.

Does the release checklist support platform-aware certification requirements for PC, console, and mobile?

Yes, the release checklist supports platform-aware certification requirements by adding specific PC, console, or mobile certification and launch items based on the target platform argument you provide during generation.

How do I prepare store metadata and distribution assets for a Go/No-Go decision?

Preparing store metadata and distribution assets for a Go/No-Go decision requires summarizing blocker counts and validating content completeness across build verification, quality gates, and store metadata preparation workflows.

Can I save the generated launch readiness checklist as a markdown artifact in my repository?

Yes, you can save the generated launch readiness checklist as a markdown artifact by writing the output directly to the production/releases/release-checklist-[version].md file path within your repository.

What project files do I need to scan for QA sign-off and build verification?

For QA sign-off and build verification, you need to read CLAUDE.md and milestone files under production/milestones, while also scanning the codebase for TODO/FIXME/HACK signals to validate production milestones.