dotnet-upgrade
Comprehensive prompts for analyzing, planning, and executing .NET framework upgrades across multi-project solutions.
- Covers the full upgrade lifecycle: project discovery and classification, dependency analysis, framework targeting, code modernization, and breaking change detection
- Includes 24+ ready-to-use prompts organized into nine categories spanning strategy, CI/CD pipeline updates, testing validation, and version control practices
- Provides guidance on using .NET Upgrade Assistant, dependency graph analysis, and automated scanning tools for enterprise-scale migrations
- Addresses NuGet package compatibility, transitive dependency resolution, async pattern conversion, and API deprecation detection with concrete validation strategies
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."
More from github/awesome-copilot
git-commit
Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping
30.2Kgh-cli
GitHub CLI (gh) comprehensive reference for repositories, issues, pull requests, Actions, projects, releases, gists, codespaces, organizations, extensions, and all GitHub operations from the command line.
21.2Kdocumentation-writer
Diátaxis Documentation Expert. An expert technical writer specializing in creating high-quality software documentation, guided by the principles and structure of the Diátaxis technical documentation authoring framework.
17.4Kprd
Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.
17.4Kexcalidraw-diagram-generator
Generate Excalidraw diagrams from natural language descriptions. Use when asked to "create a diagram", "make a flowchart", "visualize a process", "draw a system architecture", "create a mind map", or "generate an Excalidraw file". Supports flowcharts, relationship diagrams, mind maps, and system architecture diagrams. Outputs .excalidraw JSON files that can be opened directly in Excalidraw.
16.4Krefactor
Surgical code refactoring to improve maintainability without changing behavior. Covers extracting functions, renaming variables, breaking down god functions, improving type safety, eliminating code smells, and applying design patterns. Less drastic than repo-rebuilder; use for gradual improvements.
16.1K