What is the primary goal of this skill?

The primary goal is to create a 'risk-aware' planning artifact that outlines a safe, staged sequence for upgrading Godot and .NET versions, rather than performing a blind, all-at-once migration.

Can I use this for minor Godot updates?

Absolutely. It classifies upgrades into patch, minor, or major buckets and adjusts the risk assessment and validation steps accordingly.

Why does it emphasize a staged upgrade order?

Staged upgrades allow you to isolate breaking changes. By verifying the engine first, then the SDK, and then plugins, you can pinpoint the exact cause of any regressions.

What kind of output does this skill produce?

It generates a structured markdown file (upgrade-plan.md) containing the current/target state, risk areas, a recommended sequence, validation checklists, and rollback considerations.

Does this skill handle C# specific compatibility?

Yes, it specifically evaluates the .NET SDK, target frameworks, C# language versions, and NuGet package dependencies to ensure runtime and build-time stability.

Godot .NET Version Upgrade Reviewer

Name: Godot .NET Version Upgrade Reviewer
Author: LoogacyStudio

byLoogacyStudio

0•

Desarrollo de Videojuegos

Generates staged, risk-aware upgrade plans for Godot projects using .NET to ensure safe migrations across engine and SDK versions.

This skill provides a comprehensive framework for planning version upgrades in Godot and .NET environments, moving away from risky all-at-once migrations toward structured, staged transitions. It systematically evaluates engine compatibility, .NET SDK requirements, C# language features, addon stability, and export pipeline integrity. By generating a detailed upgrade-plan artifact, it helps developers identify high-risk areas, establish validation checkpoints, and define concrete rollback strategies before any breaking changes are implemented.

Características Principales

01Evaluation of addon, plugin, and NuGet package stability

02Export pipeline and CI/CD toolchain impact analysis

030 GitHub stars

04Structured rollback and branch strategy generation

05Staged upgrade sequencing to minimize migration risk

06Comprehensive assessment of Godot engine and .NET SDK compatibility

Casos de Uso

01Assessing the blast radius of third-party plugin and export template updates

02Upgrading a project to a newer .NET SDK or C# language version

03Planning a major Godot engine version migration (e.g., 4.x to 4.y)

Características Principales

01Evaluation of addon, plugin, and NuGet package stability

02Export pipeline and CI/CD toolchain impact analysis

030 GitHub stars

04Structured rollback and branch strategy generation

05Staged upgrade sequencing to minimize migration risk

06Comprehensive assessment of Godot engine and .NET SDK compatibility

Casos de Uso

01Assessing the blast radius of third-party plugin and export template updates

02Upgrading a project to a newer .NET SDK or C# language version

03Planning a major Godot engine version migration (e.g., 4.x to 4.y)