agentleFS
Sign inStart free
MRCalderon3DMRCalderon3D/everything-game-dev-code/skills/godot/godot-build-release/SKILL.md

godot-build-release

Skill105 starsChanged 8 months agoMITView on GitHub

Run Godot export, CI, and release packaging with reproducible presets and platform-aware checks.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run Godot export, CI, and release packaging with reproducible presets and platform-aware checks.

    line 11
  2. Distinctive:

    treat each platform as its own risk surface

    line 28
  3. Distinctive:

    Keep this skill aligned with the relevant rules layer and current project documentation.

    line 58
  4. Distinctive:

    If engine-specific constraints materially change the workflow, hand off to the matching engine skill or engine-specific reviewer.

    line 59

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Godot Build Release

Purpose

Run Godot export, CI, and release packaging with reproducible presets and platform-aware checks.

Use When

  • shipping Godot builds
  • export presets are fragile
  • platform packaging issues are recurring

Inputs

  • export presets
  • target platforms
  • addon state
  • release checklist

Process

  1. script or standardize export entry points
  2. capture Godot version, export preset, platform target, and addon state in logs
  3. validate startup, resources, localization, and platform assets before release candidates
  4. treat each platform as its own risk surface
  5. tie exports to QA and release readiness

Outputs

  • Godot build pipeline notes
  • platform risk list
  • artifact expectations
  • release validation targets

Quality Bar

  • respects scene-tree ownership, autoload boundaries, and resource behavior
  • keeps scripts, signals, and resources understandable at scale
  • supports export reliability and content iteration without hidden coupling

Common Failure Modes

  • autoloads becoming global dumping grounds
  • signal webs with no ownership
  • shared resources causing accidental state leakage

Related Agents

  • godot-build-resolver
  • build-engineer
  • release-manager

Related Commands

  • godot-build-fix
  • release-check
  • verify

Notes

  • Keep this skill aligned with the relevant rules layer and current project documentation.
  • If engine-specific constraints materially change the workflow, hand off to the matching engine skill or engine-specific reviewer.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free