release-checklist

Generate a pre-release validation checklist for game and application releases.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/CarlosQ96/robot-crawler --skill release-checklist-carlosq96
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-checklist
Source: https://github.com/CarlosQ96/robot-crawler/tree/main/.agents/skills/release-checklist
Command: npx skills add https://github.com/CarlosQ96/robot-crawler --skill release-checklist-carlosq96

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Produces a thorough, actionable pre-release validation checklist so teams can identify build, quality, certification, store metadata, and operational blockers before submitting a release.

Core Features & Use Cases

  • Argument-driven target selection: accepts platform scope (pc, console, mobile, all) and defaults to all when unspecified.
  • Codebase scanning: locates and tallies TODO, FIXME, and HACK annotations, and records their locations and severity for prioritization.
  • Build and QA verification: checks for test output or CI artifacts when available and enumerates build verification, performance, and content-complete gates.
  • Platform-specific requirements: appends tailored checklists for PC, console, and mobile plus store and launch readiness sections.
  • Safe save flow: presents the generated checklist and asks permission before writing to production/releases with versioned filenames.
  • Use Case: A producer preparing a milestone release runs the skill to immediately discover blocking FIXMEs, confirm certification items, and produce a store-ready checklist for sign-offs.

Quick Start

Use the release-checklist skill to generate a full pre-release checklist for the current project and target platform.

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 checklist for game and app launches across multiple platforms?

Generate a pre-release checklist by scanning project files to count TODO, FIXME, and HACK annotations, verifying build artifacts, and assembling platform-specific certification and store metadata requirements for PC, console, and mobile targets.

What should a prelaunch validation process cover to ensure store submission readiness?

A prelaunch validation process should cover codebase health, build verification, QA outputs, platform-specific certification requirements, store metadata, and operational launch gates to identify blockers before submitting a release.

Can I use a build verification checklist for both mobile and console game releases?

Yes, build verification checklists support mobile and console game releases by appending tailored platform-specific requirements alongside standard code health, QA, and store metadata validation gates.

How do I track unresolved TODO and FIXME annotations before certifying a build?

Track unresolved TODO and FIXME annotations by scanning the codebase to locate and tally these markers, recording their locations and severity to prioritize blocking issues before build certification.

What is the best way to compile launch readiness gates for a milestone release?

The best way to compile launch readiness gates is to read project milestone files, inspect available CI and test outputs, and produce a markdown checklist covering build verification, certification, and store submission requirements.

Does a pre-release validation checklist require CI test artifacts to run properly?

No, a pre-release validation checklist does not require CI test artifacts to run, but it will inspect available CI and test outputs to enumerate build verification and performance gates when they are present.