game-ci-pipeline

Generates CI/CD pipeline configurations for game builds, tests, and storefront deployment.

Updated Aug 11, 2026
One-click install
npx skills add https://github.com/zerox-core/AI_Game --skill game-ci-pipeline-zerox-core
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: game-ci-pipeline
Source: https://github.com/zerox-core/AI_Game/tree/main/.continue/skills/game-ci-pipeline
Command: npx skills add https://github.com/zerox-core/AI_Game --skill game-ci-pipeline-zerox-core

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about game-ci-pipeline

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up CI/CD for a Godot game on GitHub Actions?

Use the barichello/godot-ci Docker image pinned to your Godot version, commit export_presets.cfg to the repo, and run godot --headless --export-release for each platform preset. Run GUT tests first so failing tests block the export stage.

How do I automate Unity builds in a CI pipeline?

Use GameCI actions: unity-test-runner for EditMode and PlayMode tests, and unity-builder for platform builds. Store UNITY_LICENSE, UNITY_EMAIL, and UNITY_PASSWORD as GitHub Secrets, and cache the Library folder to cut build times significantly.

How do I deploy a game build to itch.io automatically?

Install the butler CLI in the CI job and run butler push for each platform channel such as windows, linux, or html5. Authenticate with a BUTLER_API_KEY secret and tag releases with --userversion from the git tag.

Can I deploy to Steam directly from GitHub Actions?

Yes, using game-ci/steam-deploy with a dedicated Steam builder account, a base64-encoded config.vdf, and your app ID stored as secrets. Deploy to a beta branch first and promote to the default branch manually after verification.

Why does my Godot CI export fail or produce broken binaries?

The most common cause is a version mismatch between the Docker image and the project's Godot version, since export templates are version-specific. Also verify that export preset names in the workflow match export_presets.cfg exactly, including case.

When should I use self-hosted runners for game CI?

Self-hosted runners are needed for Unreal Engine builds, which require 50-100GB of disk and a locally installed engine due to EULA restrictions on Docker distribution. Large Unity projects that exceed the 7GB RAM of free hosted runners also benefit from self-hosted hardware.