godot-4-migration
Migrate Godot 3 Projects to Godot 4
Godot 3 projects often fail after upgrading because GDScript syntax and engine APIs changed. This skill maps common Godot 3 patterns to Godot 4 replacements.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "godot-4-migration" from https://skillstore.io/skills/sickn33-godot-4-migration.md and its manifest at https://skillstore.io/api/skills/sickn33-godot-4-migration/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "godot-4-migration". A legacy exported speed variable and onready sprite reference need migration.
Expected outcome:
Recommendation: use Godot 4 annotations for both declarations. Keep the speed type explicit and verify the node reference after loading the scene.
Using "godot-4-migration". A Tween node moves a sprite and fades it at the same time.
Expected outcome:
Migration summary: create a SceneTreeTween, add the movement step, and run the fade step in parallel. Confirm both target properties in Godot 4.
Using "godot-4-migration". A script connects a signal by string and waits for a timer with yield.
Expected outcome:
Migration summary: connect the signal through its callable interface and replace yield with await. Test callback arguments and timer completion behavior.
Security Audit
SafeAll 33 external-command detections are Markdown backticks used for Godot names or fenced GDScript examples; none invokes a shell. The reconnaissance detection is an ordinary Godot error message, and no prompt injection or malicious intent appears in SKILL.md.
Risk Factors
⚙️ External commands (33)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/sickn33-godot-4-migration/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-godot-4-migration?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-godot-4-migration?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-godot-4-migration/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-godot-4-migration.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
sickn33. (2026). godot-4-migration security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-godot-4-migration/audits/5BibTeX citation
@techreport{sickn33-sickn33-godot-4-migration-2026,
author = {sickn33},
title = {godot-4-migration security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/sickn33-godot-4-migration/audits/5},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "godot-4-migration security audit report (audit version 5)"
version: "unspecified"
type: report
authors:
- name: "sickn33"
date-released: "2026-07-24"
url: "https://skillstore.io/skills/sickn33-godot-4-migration/audits/5"
identifiers:
- type: other
value: "skillstore:sickn33-godot-4-migration:audit:5"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Upgrade an Existing Game
Map common GDScript syntax and API changes before opening a Godot 3 game in Godot 4.
Teach Godot 4 Syntax
Compare old and new patterns for annotations, properties, signals, tweens, typed arrays, and coroutines.
Review a Migration
Check converted scripts for outdated patterns and identify areas that still require runtime validation.
Try These Prompts
Convert these Godot 3 declarations to Godot 4 annotations: [paste declarations]. Explain each change briefly.
Rewrite this Godot 3 Tween logic for Godot 4: [paste code]. Preserve timing, parallel behavior, and target properties.
Migrate these signal connections and coroutine calls to Godot 4: [paste code]. Identify behavior that needs runtime testing.
Review this Godot 3 script for Godot 4 migration issues: [paste script]. Prioritize changes across syntax, typing, tweens, signals, and coroutines.
Best Practices
- Migrate one subsystem at a time and test scenes after each change.
- Add explicit types where they improve compatibility and editor diagnostics.
- Verify renamed nodes, properties, signals, and resources against the target Godot documentation.
Avoid
- Do not apply syntax replacements without checking behavior changes.
- Do not assume every Godot 3 API has a direct Godot 4 equivalent.
- Do not complete a migration without running scenes and reviewing editor errors.