skills.rest
eriklieben
erikliebenCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

dev-dotnet-migrate

Migrate .NET projects across versions 8 to 11 with breaking change detection.

7|3|Updated Mar 19, 2026
Search Tags:#csharp#refactoring#migration#dotnet#upgrade#aot
One-click install
npx skills add https://github.com/eriklieben/agentic-dev-workflow --skill dev-dotnet-migrate
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev-dotnet-migrate
Source: https://github.com/eriklieben/agentic-dev-workflow/tree/main/.claude/skills/dev-dotnet-migrate
Command: npx skills add https://github.com/eriklieben/agentic-dev-workflow --skill dev-dotnet-migrate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill mitigates the risks and complexity associated with upgrading .NET versions and adopting modern features like Native AOT, ensuring incremental, verified progress across your codebase.

Core Features & Use Cases

  • Version Migration: Provides structured checklists and breaking change guidance for .NET 8 through 11.
  • AOT Readiness: Assesses project compatibility for Native AOT compilation and provides trimming guidance.
  • Nullable Adoption: Offers a phased strategy for enabling nullable reference types to eliminate null-reference exceptions.

Quick Start

Invoke the dev-dotnet-migrate skill with the 8-to-9 argument to begin the migration process for your current project.

Frequently Asked Questions about dev-dotnet-migrate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I upgrade my .NET project from version 8 to 9?▼

To upgrade .NET from version 8 to 9, invoke the migration skill with the 8-to-9 argument to receive structured checklists and breaking change guidance for systematic codebase modernization.

What is the best way to assess Native AOT compatibility in a .NET application?▼

Assessing Native AOT compatibility involves evaluating project readiness for AOT compilation and receiving trimming guidance to ensure dependencies and code paths support this modern execution mode.

How does a phased strategy for nullable reference types work in .NET?▼

A phased strategy for nullable reference types works by incrementally enabling the feature across a codebase to eliminate null-reference exceptions while maintaining test-verified progress throughout the adoption process.

Can I get breaking change detection guidance for .NET 10 and 11 migrations?▼

Yes, breaking change detection guidance is supported for migrations across .NET 8 through 11, providing structured checklists to mitigate risks and ensure verified, incremental progress during framework upgrades.

When do I need incremental migration paths for .NET framework upgrades?▼

Incremental migration paths for .NET framework upgrades are needed when modernizing a codebase to mitigate complexity, manage dependencies systematically, and ensure verified progress between versions like .NET 8 and 9.

Related Skills

Explore More Software Engineering Skills→
gutierrezp22gutierrezp22

next-upgrade

Upgrade Next.js projects to the latest stable version with codemods and dependency updates.

Community
Intermediate
TheBushidoCollectiveTheBushidoCollective
187

csharp-nullable-types

Apply C# nullable types to prevent null reference exceptions.

Official
Basic
lluppesmslluppesms

dotnet-upgrade

Analyze .NET projects and plan incremental upgrades to .NET 8.

Community
Advanced
wshaddixwshaddix
71

dotnet-add-analyzers

Configure .NET analyzers, severity overrides, and trimming compatibility via EditorConfig.

Community
Intermediate