skilld
All skills
thedivergentai avatar

/godot-version-migration

@57c9225
by Divergent AIthedivergentai/gd-agentic-skills783 stars
48

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.

Ask your Agent

Use this Skill: https://skilld.dev/gh/thedivergentai/gd-agentic-skills/godot-version-migration

This session only. Nothing lands on disk.

SKILL.md

≈119 tokens always: the name and description. ≈1.5k when used: this file. ≈86k more on demand in 99 files.

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 (config_version, 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.

Hop table

Majors / bridges

Era Resource
1.x archaeology legacy/pre-2-context.md
2.x → 3.x legacy/2-to-3.md
3.x → 4.0 bridges/3-to-4.md · official guide
Ladder overview era-index.md

4.x minors

Hop Official guide
4.0 → 4.1 https://docs.godotengine.org/en/stable/tutorials/migrating/upgrading_to_godot_4.1.html
4.1 → 4.2 https://docs.godotengine.org/en/stable/tutorials/migrating/upgrading_to_godot_4.2.html
4.2 → 4.3 https://docs.godotengine.org/en/stable/tutorials/migrating/upgrading_to_godot_4.3.html
4.3 → 4.4 https://docs.godotengine.org/en/stable/tutorials/migrating/upgrading_to_godot_4.4.html
4.4 → 4.5 https://docs.godotengine.org/en/stable/tutorials/migrating/upgrading_to_godot_4.5.html
4.5 → 4.6 https://docs.godotengine.org/en/stable/tutorials/migrating/upgrading_to_godot_4.6.html
4.6 → 4.7 https://docs.godotengine.org/en/stable/tutorials/migrating/upgrading_to_godot_4.7.html

Cross-skill checklist: references/hop-index.md

Module directory

Mirrored Domain Skill migration notes live at references/<topic>.md (e.g. references/2d-physics.md). Hub-native legacy/, bridges/, and era-index.md are not Domain Skill mirrors.

sync_godot_version_migration.py --all

Reference

Official docs

Related Skills

Master
  • godot-master — Library router for current Domain Skill modules after migration is complete.
Downstream / consumers
  • godot-analyst — Score architecture on the target APIs after hops land.
  • godot-auditor — Never-list / legacy-syntax verification after upgrades.
  • godot-builder — CI / headless bake against the new engine target after each hop.
Complements

Source: SKILL.md on GitHub

Third-party checks

No alerts1mo3 checks · Risk SAFE
  • Gen Agent Trust Hub1mo

    The skill is a comprehensive documentation and orchestration hub for migrating Godot engine projects across various versions. It provides structured guidance, checklists, and references to official and community documentation to ensure a safe and stable upgrade path.

  • Socket1mo

    No alerts

  • Snyk1mo

    Risk: LOW · No issues

Provenance

Signed by skilld at 57c9225. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 3 weeks ago.

Activeupdated 2 months ago

README badge

README badge for thedivergentai/gd-agentic-skills/godot-version-migration