Godot Version Migration

Community

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.

Overview

Publisher	thedivergentai
Repository	`GD-Agentic-Skills`
Skill name	`godot-version-migration`
Stars	782
Forks	48
Bundled files	99
License	LGPL-3.0
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
99 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by thedivergentai on GitHub. Read the source before you install it.

Installation

Install the Godot Version Migration AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/thedivergentai/GD-Agentic-Skills/tree/main/skills/godot-version-migration
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/thedivergentai/GD-Agentic-Skills/tree/main/skills/godot-version-migration

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/thedivergentai/GD-Agentic-Skills.git /tmp/GD-Agentic-Skills
mkdir -p .claude/skills
cp -r /tmp/GD-Agentic-Skills/skills/godot-version-migration .claude/skills/godot-version-migration

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Godot Version Migration in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Godot Version Migration on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Godot Version Migration is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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

Read project.godot (config_version, config/features) or legacy engine.cfg.
Ask the user if files are ambiguous.
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)

While current < 4.7, perform exactly one hop to current + 0.1.
Open the official upgrading page for the destination version.
From hop-index.md, open only module notes for subsystems present in the project.
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.

text
sync_godot_version_migration.py --all

Reference

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

godot-project-foundations — Project settings / structure once on the target version.
godot-gdscript-mastery — Typed GDScript 2.0 idioms after 3→4 / 4.x language hops.
godot-export-builds — Re-validate exports after each hop that touches platforms.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

and 39 more files.

Frequently asked questions

What does the Godot Version Migration AI skill do?

Why use Godot Version Migration on TypingMind?

Because you install it once and use it with any model. Godot Version Migration is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Godot Version Migration in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/thedivergentai/GD-Agentic-Skills/tree/main/skills/godot-version-migration. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Godot Version Migration?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Godot Version Migration?

As many as you like. As long as a model supports skills, you can use Godot Version Migration with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Godot Version Migration AI skill free?

Yes. It is published on GitHub by thedivergentai under the LGPL-3.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Concept Diagrams

NousResearch

OrganizationPopular

Generate flat, minimal educational SVG visuals as HTML.

Hyperframes

Render MP4/WebM videos from HTML compositions.

Ip As Logo

Design minimal cute IP mascot marks readable at 32px.

Mono Color

Generate one- or two-ink editorial print poster images.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Godot Version Migration

NEVER Do

Version detect

Workflow router (MANDATORY)

Steps (4.x minors)

Hop table

Majors / bridges

4.x minors

Module directory

Reference

Official docs

Related Skills

Master

Downstream / consumers

Complements

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now