release-checklist

To generate a pre-release validation checklist, use an automated skill that scans project context and codebase health to identify blockers across build verification, certification, and store metadata. It requires read access to project configuration files and milestone documentation to ensure accurate release status reporting.

A game deployment readiness check covers codebase health, build integrity, quality gates, certification requirements, and store metadata. It scans for blockers and quality gaps tailored to specific platforms like PC, console, or mobile to ensure comprehensive launch readiness.

Yes, you can validate Steam store metadata and achievements before pushing a build. The validation process generates a platform-specific checklist for PC releases that verifies metadata, achievements, and controller support requirements are fully met.

To check codebase health for console or mobile deployment, the validation process scans project context and identifies quality gaps. It generates tailored checklists that confirm build verification and certification requirements are satisfied across multiple platforms.

Yes, you need project configuration files and milestone documentation to verify launch readiness. The validation process requires read access to these files to accurately scan project context and report the current release status.

The best way to identify quality gaps before a game release is to use an automated validation checklist. It systematically scans your codebase health, build integrity, and quality gates to detect blockers and ensure all platform-specific requirements are satisfied.