steam-build-automation

Automate Steam depot uploads with SteamPipe CI/CD pipelines for GitHub Actions, GitLab CI, and Docker.

1|Updated Mar 26, 2026

Search Tags:#devops #ci/cd #github actions #build automation #steam #steampipe #steamcmd

One-click install

npx skills add https://github.com/TMHSDigital/Steam-Cursor-Plugin --skill steam-build-automation-tmhsdigital

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: steam-build-automation
Source: https://github.com/TMHSDigital/Steam-Cursor-Plugin/tree/main/skills/steam-build-automation
Command: npx skills add https://github.com/TMHSDigital/Steam-Cursor-Plugin --skill steam-build-automation-tmhsdigital

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually uploading game builds to Steam through steamcmd is repetitive and error-prone, especially when managing depot IDs, branch promotion, and Steam Guard credentials across releases. This Skill generates complete CI/CD configurations that automate the entire SteamPipe build upload flow. ## Core Features & Use Cases - CI Pipeline Generation: Produces ready-to-use GitHub Actions and GitLab CI configurations that install steamcmd, restore cached credentials, and run app_build.vdf uploads on version tags. - Docker-Based Builds: Provides Dockerfile patterns using the cm2network/steamcmd image for consistent, reproducible build environments. - Branch & Secrets Management: Covers beta vs default branch strategies via the VDF setlive field, plus best practices for storing config.vdf and build account credentials as CI secrets. - Use Case: A developer pushing a v1.2.0 tag wants their Unity game automatically uploaded to Steam depots for Windows and Linux, landing on the beta branch for QA before manual promotion to default. ## Quick Start Set up a GitHub Actions workflow that uploads my game with App ID 2345678 to the Steam beta branch whenever I push a version tag.

Frequently Asked Questions about steam-build-automation

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

FAQPage Schema

How do I automate Steam build uploads with GitHub Actions?▼

Create a workflow that installs steamcmd, restores a base64-encoded config.vdf from GitHub Secrets, then runs steamcmd with +login and +run_app_build pointing to your app_build.vdf. Trigger it on version tags so uploads happen only on releases.

How to handle Steam Guard in CI/CD pipelines?▼

Run steamcmd interactively once on a local machine to complete Steam Guard, then extract the cached config.vdf from the Steam config directory. Store it base64-encoded as a CI secret and restore it in the pipeline before login.

Can I use Docker for SteamPipe build uploads?▼

Yes, the cm2network/steamcmd Docker image provides a preconfigured steamcmd environment. Copy your steamworks VDF files and build artifacts into the image and set the entrypoint to steamcmd with login and run_app_build commands.

Should CI push Steam builds to the default branch?▼

No, pushing directly to default releases the build to all users immediately. Set the VDF setlive field to beta for automated uploads, test on the beta branch, then manually promote to default in the Steamworks Partner site.

Why does steamcmd hang in my CI pipeline?▼

steamcmd hangs when the command chain lacks an explicit +quit at the end. Always terminate your steamcmd invocation with +quit so the process exits after the build upload completes.