Verified:GitHub

version-upgrade

Upgrades .NET repositories to a target framework version and produces a GitLab MR-ready report.

Updated Jul 22, 2026

Search Tags:#migration #dotnet #gitlab #upgrade #ci-cd #nuget #target-framework

One-click install

npx skills add https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc --skill version-upgrade-trigent-software-pvt-ltd

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: version-upgrade
Source: https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc/tree/main/plugins/dotnet/skills/version-upgrade
Command: npx skills add https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc --skill version-upgrade-trigent-software-pvt-ltd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Upgrading .NET repositories across projects, packages, SDK pins, and CI pipelines is error-prone and manual. This Skill automates the safe mechanical parts of a .NET version upgrade while flagging risky packages and breaking-change areas for human review. ## Core Features & Use Cases - Repository Scanning: Detects target frameworks, project types (Web API, Azure Functions, class libraries, test projects), package management style, and GitLab CI SDK references. - Safe Mechanical Upgrades: Updates TargetFramework values, global.json SDK pins, and optionally package versions, Central Package Management, Directory.Build.props, and .slnx migration behind explicit flags. - Risk-Aware Reporting: Flags risky packages (EF Core, Npgsql, MassTransit, Swashbuckle, etc.), runs build/test validation, and generates a GitLab MR-ready upgrade report with risks and follow-up items. - Use Case: A team needs to move a Web API from .NET 8 to .NET 10. Run the skill with the target framework to scan the repo, apply safe changes, validate the build, and receive a complete MR description with manual follow-up items. ## Quick Start Ask the AI to upgrade this repository to .NET 10 and generate an upgrade report for a GitLab merge request.

Frequently Asked Questions about version-upgrade

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

FAQPage Schema

How do I upgrade a .NET project from .NET 8 to .NET 10?▼

Run the skill with the target framework, for example net10.0. It scans the repo, updates TargetFramework values and global.json, validates with dotnet build, and produces an upgrade report with risks and manual follow-up items.

Can I preview .NET upgrade changes without modifying files?▼

Yes, pass the --report-only flag. The skill performs the full scan and analysis, then generates the upgrade report describing planned changes without editing any project files, packages, or CI configuration.

Does the .NET upgrade automatically update NuGet package versions?▼

No, package upgrades require the --allow-packages flag. Even then, risky packages like Entity Framework Core, Npgsql, MassTransit, and Swashbuckle are only flagged for manual review, never silently upgraded.

Does it support Azure Functions in-process to isolated worker migration?▼

It detects in-process Azure Functions and flags them as high-risk since the model is unsupported in .NET 10+, but it does not auto-migrate. Migration requires --allow-breaking-changes and explicit user confirmation.

What happens if the build fails after a .NET upgrade?▼

The skill reports the full error output without hiding failures. It proposes targeted fixes only for errors directly related to the TFM upgrade and does not attempt to fix unrelated pre-existing build errors.

Can it migrate to Central Package Management or .slnx format?▼

Yes, but only with explicit opt-in flags. Use --allow-cpm to migrate package versions into Directory.Packages.props, and --allow-slnx to generate a modern .slnx solution file alongside the existing .sln.