ci-cd-automation_skill

Overview

This skill automates CI/CD pipelines, build orchestration, and automated testing tailored for game development workflows. It provides engine-specific patterns for Unity and Unreal, plus optimization and deployment strategies to reduce build time and increase release reliability. The focus is practical: faster feedback, repeatable builds, and controlled deployments across platforms.

How this skill works

It defines staged pipelines that validate, test, build in parallel, and deploy to gated environments. The skill supplies GitHub Actions examples for Unity and Unreal, caching and matrix build patterns, playmode/unit test integration, artifact handling, and staging/prod deployment steps. It also recommends build optimization techniques and troubleshooting tactics to stabilize pipelines.

When to use it

• Setting up CI for a new game project across multiple target platforms
• Adding automated PlayMode and integration tests to catch regressions early
• Optimizing slow build times with caching and parallelization
• Deploying WebGL, desktop, mobile, or server builds to staging and production
• Creating gated release flows with approvals and environment promotion

Best practices

• Cache engine-specific Library or intermediate folders to cut rebuild time
• Use matrix builds to parallelize platform outputs and upload artifacts per target
• Run linting and quick validation on push; run full tests on PRs or scheduled runs
• Isolate flaky tests, add timeouts, and retry network-sensitive tests
• Adopt semantic or automated versioning and artifact retention policies

Example use cases

• Unity project: GitHub Actions pipeline with library caching, game-ci test runner, parallel builds for Windows/Linux/WebGL, and staged deploy to S3
• Unreal project: self-hosted runner building via RunUAT, uploading build artifacts for QA
• Mobile pipeline: matrix build for Android/iOS, artifact signing step, and canary rollout to testers
• Server builds: rolling deployment strategy for multiplayer servers with incremental builds and health checks
• Optimization sprint: introduce incremental builds, split asset bundles, and move heavy tasks to self-hosted runners