release-checklist

Name: release-checklist
Availability: InStock
Author: scomofo

Generate a pre-release validation checklist with build verification and quality gates.

Updated Mar 28, 2026

Search Tags:#quality gates #build verification #codebase health #pre-launch validation #release checklist #platform compliance #store readiness

Ready to run

npx skills add https://github.com/scomofo/dragon-forge --skill release-checklist-scomofo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release-checklist
Source: https://github.com/scomofo/dragon-forge/tree/main/.agents/skills/release-checklist
Command: npx skills add https://github.com/scomofo/dragon-forge --skill release-checklist-scomofo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of launching with an incomplete build, unverified quality gates, or missing store and launch readiness items by turning your current project state into a structured, auditable release checklist.

Core Features & Use Cases

Platform-scoped checklist generation: Produces PC, console, and/or mobile requirement sections based on the platform argument.
Codebase health scanning: Counts TODO/FIXME/HACK items and summarizes their locations to surface blockers.
Release gate output with sign-offs: Produces a save-ready checklist including rationale, blockers, and required sign-offs for a go/no-go decision.
Use Case: Before cutting a Dragon Forge release for the current sprint/milestone, run the skill to validate build health, test expectations, and store/launch readiness in one place.

Quick Start

Ask the AI to run the release-checklist for all platforms and then save the generated checklist for the current version.

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 launch validation?▼

To generate a pre-release checklist for game launch validation, the skill parses AGENTS.md and milestone files, scans the repository for TODO/FIXME/HACK items, and outputs a structured artifact covering build verification and quality gates.

Does pre-launch validation work for multi-platform releases across PC, console, and mobile?▼

Pre-launch validation supports multi-platform releases by generating platform-scoped requirement sections for PC, console, and mobile, ensuring store readiness and platform compliance are validated for each targeted environment.

What is codebase health scanning and how does it identify release blockers?▼

Codebase health scanning identifies release blockers by counting TODO, FIXME, and HACK items across the repository and summarizing their locations to surface incomplete code that may prevent a successful launch.

How do I create an auditable release gate with required sign-offs for a go/no-go decision?▼

You can create an auditable release gate by running this skill to produce a save-ready checklist that includes rationale, identified blockers, and required sign-offs, which can be written to production/releases/release-checklist-[version].md.

Can I use this release checklist skill without any external dependencies?▼

Yes, you can use this release checklist skill without external dependencies, as it operates independently by parsing existing project files and scanning the codebase directly to produce the launch readiness validation artifact.

When should I run pre-launch validation to ensure store readiness and content completion?▼

You should run pre-launch validation before cutting a release for a current sprint or milestone to ensure build health, test expectations, content completion, and store readiness are verified in a single auditable checklist.