Dotnet Upgrade
GitHubOfficialOriginally contributed by @oleksiyyurchyna as prompts/dotnet-upgrade.prompt.md; moved into a skill by pull request #761Distributed by GitHub
- Skill
- Guidelines
- Software development
- MIT
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
The dotnet-upgrade skill provides a structured collection of prompts designed to guide developers through the complex process of migrating legacy .NET applications to modern .NET versions. It covers the entire lifecycle of an upgrade, from initial project assessment and dependency analysis to CI/CD pipeline modernization, testing strategies, and final deployment validation. By leveraging these prompts, teams can systematically identify breaking changes, manage NuGet dependencies, refactor code patterns, and ensure a stable transition to newer framework targets.
What it does
- Analyzes project types and target framework compatibility.
- Identifies legacy dependencies and suggests modern alternatives.
- Provides strategies for incremental upgrades and rollback planning.
- Generates guidance for updating CI/CD build pipelines.
- Outlines testing and validation procedures for post-upgrade verification.
- Offers templates for documentation and stakeholder communication.
When to use it
- When planning a migration from .NET Framework to .NET 8 or newer.
- When assessing the complexity of a large solution with multiple dependencies.
- When needing to modernize build configurations and CI/CD pipelines.
- When establishing a structured approach for regression testing during an upgrade.
- When documenting upgrade progress and communicating changes to stakeholders.
Advantages
- Reduces manual effort in identifying breaking changes and deprecated APIs.
- Ensures a consistent and repeatable upgrade process across multiple projects.
- Helps mitigate risks through structured rollback and validation planning.
- Facilitates better team coordination via standardized PR and documentation templates.
Usage examples
- “Analyze my solution and identify all projects that still use packages.config and need migration to PackageReference.”
- The agent will scan the solution files, list the projects using legacy package management, and provide a step-by-step guide on how to convert them to the modern format.
- “Recommend an upgrade order for my solution and suggest how to isolate class library upgrades from API migrations.”
- The agent will analyze the dependency graph and propose a sequence that minimizes build errors, prioritizing low-level libraries before moving to application-level components.
Install
Download the skill as a ZIP:
https://autogineer.com/agent-skills/github/dotnet-upgrade-s34x/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip dotnet-upgrade.zip -d .agents/skills
Documentation by oleksiyyurchyna
Project Discovery & Assessment
name: "Project Classification Analysis" prompt: "Identify all projects in the solution and classify them by type (
.NET Framework,.NET Core,.NET Standard). Analyze each.csprojfor its currentTargetFrameworkand SDK usage."name: "Dependency Compatibility Review" prompt: "Review external and internal dependencies for framework compatibility. Determine the upgrade complexity based on dependency graph depth."
name: "Legacy Package Detection" prompt: "Identify legacy
packages.configprojects needing migration toPackageReferenceformat."
Upgrade Strategy & Sequencing
name: "Project Upgrade Ordering" prompt: "Recommend a project upgrade order from least to most dependent components. Suggest how to isolate class library upgrades before API or Azure Function migrations."
name: "Incremental Strategy Planning" prompt: "Propose an incremental upgrade strategy with rollback checkpoints. Evaluate the use of Upgrade Assistant or manual upgrades based on project structure."
name: "Progress Tracking Setup" prompt: "Generate an upgrade checklist for tracking build, test, and deployment readiness across all projects."
Framework Targeting & Code Adjustments
name: "Target Framework Selection" prompt: "Suggest the correct
TargetFrameworkfor each project (e.g.,net8.0). Review and update deprecated SDK or build configurations."name: "Code Modernization Analysis" prompt: "Identify code patterns needing modernization (e.g.,
WebHostBuilder→HostBuilder). Suggest replacements for deprecated .NET APIs and third-party libraries."name: "Async Pattern Conversion" prompt: "Recommend conversion of synchronous calls to async where appropriate for improved performance and scalability."
NuGet & Dependency Management
name: "Package Compatibility Analysis" prompt: "Analyze outdated or incompatible NuGet packages and suggest compatible versions. Identify third-party libraries that lack .NET 8 support and provide migration paths."
name: "Shared Dependency Strategy" prompt: "Recommend strategies for handling shared dependency upgrades across projects. Evaluate usage of legacy packages and suggest alternatives in Microsoft-supported namespaces."
name: "Transitive Dependency Review" prompt: "Review transitive dependencies and potential version conflicts after upgrade. Suggest resolution strategies for dependency conflicts."
CI/CD & Build Pipeline Updates
name: "Pipeline Configuration Analysis" prompt: "Analyze YAML build definitions for SDK version pinning and recommend updates. Suggest modifications for
UseDotNet@2andNuGetToolInstallertasks."name: "Build Pipeline Modernization" prompt: "Generate updated build pipeline snippets for .NET 8 migration. Recommend validation builds on feature branches before merging to main."
name: "CI Automation Enhancement" prompt: "Identify opportunities to automate test and build verification in CI pipelines. Suggest strategies for continuous integration validation."
Testing & Validation
name: "Build Validation Strategy" prompt: "Propose validation checks to ensure the upgraded solution builds and runs successfully. Recommend automated test execution for unit and integration suites post-upgrade."
name: "Service Integration Verification" prompt: "Generate validation steps to verify logging, telemetry, and service connectivity. Suggest strategies for verifying backward compatibility and runtime behavior."
name: "Deployment Readiness Check" prompt: "Recommend UAT deployment verification steps before production rollout. Create comprehensive testing scenarios for upgraded components."
Breaking Change Analysis
name: "API Deprecation Detection" prompt: "Identify deprecated APIs or removed namespaces between target versions. Suggest automated scanning using
.NET Upgrade Assistantand API Analyzer."name: "API Replacement Strategy" prompt: "Recommend replacement APIs or libraries for known breaking areas. Review configuration changes such as
Startup.cs→Program.csrefactoring."name: "Regression Testing Focus" prompt: "Suggest regression testing scenarios focused on upgraded API endpoints or services. Create test plans for critical functionality validation."
Version Control & Commit Strategy
name: "Branching Strategy Planning" prompt: "Recommend branching strategy for safe upgrade with rollback capability. Generate commit templates for partial and complete project upgrades."
name: "PR Structure Optimization" prompt: "Suggest best practices for creating structured PRs (
Upgrade to .NET [Version]). Identify tagging strategies for PRs involving breaking changes."name: "Code Review Guidelines" prompt: "Recommend peer review focus areas (build, test, and dependency validation). Create checklists for effective upgrade reviews."
Documentation & Communication
name: "Upgrade Documentation Strategy" prompt: "Suggest how to document each project's framework change in the PR. Propose automated release note generation summarizing upgrades and test results."
name: "Stakeholder Communication" prompt: "Recommend communicating version upgrades and migration timelines to consumers. Generate documentation templates for dependency updates and validation results."
name: "Progress Tracking Systems" prompt: "Suggest maintaining an upgrade summary dashboard or markdown checklist. Create templates for tracking upgrade progress across multiple projects."
Tools & Automation
name: "Upgrade Tool Selection" prompt: "Recommend when and how to use:
.NET Upgrade Assistant,dotnet list package --outdated,dotnet migrate, andgraph.jsondependency visualization."name: "Analysis Script Generation" prompt: "Generate scripts or prompts for analyzing dependency graphs before upgrading. Propose AI-assisted prompts for Copilot to identify upgrade issues automatically."
name: "Multi-Repository Validation" prompt: "Suggest how to validate automation output across multiple repositories. Create standardized validation workflows for enterprise-scale upgrades."
Final Validation & Delivery
name: "Final Solution Validation" prompt: "Generate validation steps to confirm the final upgraded solution passes all validation checks. Suggest production deployment verification steps post-upgrade."
name: "Deployment Readiness Confirmation" prompt: "Recommend generating final test results and build artifacts. Create a checklist summarizing completion across projects (builds/tests/deployment)."
name: "Release Documentation" prompt: "Generate a release note summarizing framework changes and CI/CD updates. Create comprehensive upgrade summary documentation."
Files
- ATTRIBUTION.mdAdded by AutoGineer1.1 KiB
- LICENSELicence file added by AutoGineer1.0 KiB
- SKILL.md6.9 KiB
Requirements and compatibility
Written for: GitHub Copilot
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Security
No issues found by our static scan· No issues found
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Originally contributed by
@oleksiyyurchynaas prompts/dotnet-upgrade.prompt.mdmoved into a skill by pull request #761
- Publisher
- GitHub (Official)
- Distributed by
- GitHub
- Source
- github/awesome-copilot · skills/dotnet-upgrade · commit 797337f
- Licence
- MIT License (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
- Contributors
- Arggon, oleksiyyurchyna
AutoGineer is not affiliated with or endorsed by oleksiyyurchyna or GitHub.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download dotnet-upgrade.zip