Godot Export Builds

This covers the full export pipeline for shipping Godot games to Windows, Linux, macOS, Android, iOS, and Web. It includes headless command-line exports for CI/CD, platform-specific gotchas like macOS notarization and Android signing, and practical scripts for GitHub Actions workflows, Steam uploads, and PCK patching for updates. The "NEVER" rules are worth reading if you've shipped a build that crashed on mobile but worked fine in editor, or accidentally committed a keystore to Git. Most useful when you're setting up automated builds or need to reduce your 500MB web export to something reasonable. The feature flag patterns help you strip debug commands from production without littering your code with conditionals.

skills.sh installs: 246
GitHub stars: 464
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add thedivergentai/gd-agentic-skills --skill godot-export-builds --agent claude-code

Installs into .claude/skills of the current project.

Files

Export & Builds

Headless / CI / platform release plumbing — not Editor → Export click-path tutorials.

NEVER Do (Expert Export Rules)

Platform & Validation

NEVER export to production without a smoke test — Editor play ≠ Web/Mobile/Console constraints.
NEVER skip macOS notarization for direct distribution — Gatekeeper blocks unsigned apps (Steam/App Store distribution can substitute).
NEVER use ad-hoc writable res:// paths in builds — Saves/logs go to user://.

Performance & Size

NEVER ship Debug templates as release — Use --export-release.
NEVER include raw authoring junk — Filter .md / .psd / docs out of presets.
NEVER ignore VRAM compression on Web/Mobile — Enable ASTC/ETC2 (keep pixel art uncompressed).

Security

NEVER commit keystores or passwords — Env vars + export_android_signing_env.ps1.
NEVER leave debug cheats in release — Gate with OS.has_feature("release").
NEVER enable Shader Baker on dedicated server exports — Wasted build time; baker is for visual clients.