What problem does it solve? Game teams often build and upload releases manually, which is slow and error-prone. This Skill produces copy-paste-ready CI/CD configurations that automate testing, multi-platform builds, and deployment to Steam, itch.io, or Epic Games Store. ## Core Features & Use Cases - Engine-Specific Pipelines: Generates complete GitHub Actions workflows for Godot (barichello/godot-ci), Unity (GameCI), and Unreal Engine (self-hosted runners with BuildCookRun or BuildGraph). - Storefront Deployment Automation: Configures steamcmd-based Steam deploys to beta branches, butler pushes to itch.io channels, and BuildPatchTool uploads for Epic. - Versioning and Artifact Management: Provides git-tag-based versioning strategies, build number injection, and artifact retention policies. - Use Case: A Godot indie team with no CI asks for an automated pipeline; the Skill detects the engine from project.godot and outputs a workflow that runs GUT tests, exports Windows/Linux/Web builds, and pushes tagged releases to itch.io via butler. ## Quick Start Ask the assistant to set up a CI pipeline for your game project, specifying the engine and deployment target, for example: set up a GitHub Actions pipeline to build my Godot 4.4 game and deploy it to itch.io.