game-ci-cd-pipeline — Claude Code skill: Unity/Unreal CI/CD setup
game-ci-cd-pipeline scopes a messy Unity or Unreal build setup by signal tier first, then settles on one narrow pipeline packet to repair.
no license 297 installs ★ 61 updated 2026-11-19
npx skills add akillness/jeo-skills --skill game-ci-cd-pipeline -a claude-codeWhat game-ci-cd-pipeline does
The skill treats a shaky game pipeline as a scoping problem. Before touching workflow files it asks which lane the pain lives in: a fast branch gate, a nightly package candidate for QA, or a release candidate headed for certification. Get that wrong and the fixes land in the wrong place.
After that it settles on a single packet — first pipeline, stage split, cache policy, preflight for SDK and signing, artifact handoff, or tighter CI feedback. Three reference files carry the detail: references/intake-packets-and-route-outs.md, references/pipeline-patterns.md and references/signal-tiers-and-promotion-lanes.md. File work goes through Bash, Read, Write, Edit, Glob and Grep.
Expect an audit and a written brief rather than a deployer: shipping builds and rotating secrets are outside what it does. When the whole complaint is one red build log, it hands off to game-build-log-triage instead of redesigning everything around a single failure.
What it helps with
- set up a first reproducible Unity pipeline instead of hand-run builds
- split restore, build, cook and package so the failing stage is obvious
- stop guessing which directories belong in the build cache
- catch missing SDK and signing setup before expensive packaging starts
- fix artifact naming and the handoff of candidates to QA
Example prompts for the agent
- Our Unity GitHub Actions job packages on every branch and pull requests crawl. Scope the fix.
- Plan a nightly QA candidate lane for Unreal on Windows and Android, starting from the signal tier.
- Write the release candidate brief: artifact names, retention, and who approves promotion.
How to install game-ci-cd-pipeline
1Skills CLI (Vercel)
npx skills add akillness/jeo-skills --skill game-ci-cd-pipeline -a claude-code2Manually: put the files in place
~/.claude/skills/game-ci-cd-pipeline/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/game-ci-cd-pipeline/
1Skills CLI (Vercel)
npx skills add akillness/jeo-skills --skill game-ci-cd-pipeline -a codex2Manually: put the files in place
.agents/skills/game-ci-cd-pipeline/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add akillness/jeo-skills --skill game-ci-cd-pipeline -a cursor2Manually: put the files in place
.cursor/skills/game-ci-cd-pipeline/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install akillness/jeo-skills .agent-skills/game-ci-cd-pipeline/SKILL.md2Manually: put the files in place
.github/skills/game-ci-cd-pipeline/SKILL.md1Skills CLI (Vercel)
npx skills add akillness/jeo-skills --skill game-ci-cd-pipeline -a gemini-cli2Platform CLI
gemini skills install https://github.com/akillness/jeo-skills --path .agent-skills/game-ci-cd-pipelineManually: put the files in place
.devin/skills/game-ci-cd-pipeline/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add akillness/jeo-skills --skill game-ci-cd-pipeline -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about game-ci-cd-pipeline
How do I install game-ci-cd-pipeline in Claude Code?
Run npx skills add akillness/jeo-skills --skill game-ci-cd-pipeline -a claude-code. The skill file then sits at ~/.claude/skills/game-ci-cd-pipeline/SKILL.md.
What does game-ci-cd-pipeline do?
It names the signal tier — branch gate, nightly QA candidate or release candidate — and picks one packet to work on: pipeline setup, stage split, cache policy, preflight readiness, artifacts or CI signal.
How is it different from game-build-log-triage?
This skill fixes the shape of the pipeline itself. When the job is a first pass over one red log, it routes there instead.