Comprehensive prompts for analyzing, planning, and executing .NET framework upgrades across multi-project solutions.
Works with
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 Assistan
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiondotnet-upgradeExecute the skills CLI command in your project's root directory to begin installation:
Fetches dotnet-upgrade from github/awesome-copilot and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate dotnet-upgrade. Access via /dotnet-upgrade in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
28.7K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
28.7K
stars
name: "Project Classification Analysis"
prompt: "Identify all projects in the solution and classify them by type (.NET Framework, .NET Core, .NET Standard). Analyze each .csproj for its current TargetFramework and 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.config projects needing migration to PackageReference format."
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."
name: "Target Framework Selection"
prompt: "Suggest the correct TargetFramework for 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."
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."
name: "Pipeline Configuration Analysis"
prompt: "Analyze YAML build definitions for SDK version pinning and recommend updates. Suggest modifications for UseDotNet@2 and NuGetToolInstaller tasks."
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."
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."
name: "API Deprecation Detection"
prompt: "Identify deprecated APIs or removed namespaces between target versions. Suggest automated scanning using .NET Upgrade Assistant and API Analyzer."
name: "API Replacement Strategy"
prompt: "Recommend replacement APIs or libraries for known breaking areas. Review configuration changes such as Startup.cs → Program.cs refactoring."
name: "Regression Testing Focus" prompt: "Suggest regression testing scenarios focused on upgraded API endpoints or services. Create test plans for critical functionality validation."
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."
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."
name: "Upgrade Tool Selection"
prompt: "Recommend when and how to use: .NET Upgrade Assistant, dotnet list package --outdated, dotnet migrate, and graph.json dependency 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."
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."
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
github/awesome-copilot
github/awesome-copilot
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
Solid pick for teams standardizing on skills: dotnet-upgrade is focused, and the summary matches what you get after install.
dotnet-upgrade has been reliable in day-to-day use. Documentation quality is above average for community skills.
dotnet-upgrade has been reliable in day-to-day use. Documentation quality is above average for community skills.
I recommend dotnet-upgrade for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
dotnet-upgrade is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
dotnet-upgrade fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
dotnet-upgrade has been reliable in day-to-day use. Documentation quality is above average for community skills.
Solid pick for teams standardizing on skills: dotnet-upgrade is focused, and the summary matches what you get after install.
Registry listing for dotnet-upgrade matched our evaluation — installs cleanly and behaves as described in the markdown.
dotnet-upgrade is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 52