Agent skill · thedivergentai
godot-version-migration
Full-history Godot version migration hub. Use when upgrading any Godot project toward the library target (currently 4.7)—from 1.x/2.x legacy eras through 3→4 and hop-by-hop 4.x minors—or finding Domain Skill-scoped migration notes. Trigger keywords: upgrade Godot, migrate Godot version, Godot 3 to 4, Godot 2 to 3, upgrading_to_godot, version migration, breaking changes, convert-3to4, TileMapLayer, AnimationMixer, engine.cfg, project.godot.
What it needs
About 3k tokens when loaded.
What this skill does
Godot Version Migration Orchestrator for engine version upgrades from early Godot through the library target. Domain Skills document current APIs; this hub owns the upgrade path. Library target: Godot 4.7+ Corpus: docs changelog · interactive changelog · download archive · GitHub releases · migrating index NEVER Do NEVER skip majors — route 1.x → 2.x → latest 3.x → 4.0 before any 4.x minor ladder. NEVER skip 4.x hops — upgrade 4.0 → 4.1 → … → 4.7 one minor at a time; stabilize after each hop. NEVER claim automatic 1.x→4.x conversion or bit-exact autopilot. NEVER treat Domain Skill bodies as migration changelogs — load references/<topic>.md (mirrored from each skill’s references/migration-notes.md). NEVER load all module notes at once — only subsystems present in the project. NEVER mix server/client Godot minors for high-level multiplayer (especially across 4.2→4.3 SceneMultiplayer protocol changes). NEVER choose Mesh “Restart & Upgrade” without VCS backup (4.1→4.2 mesh format). NEVER run the 3→4 converter without a full backup (tool does not backup). Version detect 1. Read project.godot (configversion, config/features) or legacy engine.cfg. 2. Ask the user if files are ambiguous. 3. Map to an era in references/era-index.md. Workflow router (MANDATORY) Detected era Load Do NOT -------------- ------ -------- 1.x / early 2 legacy/pre-2-context.md Invent a 1→4 converter 2.x legacy/2-to-3.md then stabilize on latest 3.x Jump straight to 4.7 notes 3.x bridges/3-to-4.md + official 3→4 guide Skip latest-3.x stabilize gate 4.x < 4.7 Official hop guide + hop-index.md module notes for touched systems Skip minors Already 4.7+ godot-master / Domain Skills Treat this hub as a coding tutorial Steps (4.x minors) 1. While current < 4.7, perform exactly one hop to current + 0.1. 2. Open the official upgrading page for the destination version. 3. From hop-index.md, open only module notes for subsystems present in the project. 4. Apply fixes; open in the new editor; playtest; repeat. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills thedivergentai/godot-version-migration