- Home
- Skills
- Code Quality & Review
- .NET Upgrade Planner
More screenshots
Works with the AI Agents you already use
.NET Upgrade Planner
Plans and validates .NET target framework upgrades by fetching live breaking changes and running regression tests.
Free
.NET Upgrade Planner
Example session with this skill installed
Plan the upgrade from net6.0 to net10.0 for UpgradeLab.sln with the dotnet-upgrade-planner skill. I approve the baseline test run, the live doc fetches, the TFM and package-version diff, the breaking-change fixes, and the rebuild/retest.
- Read your context and instructions
- Compiled the net upgrade planner
.NET upgrade plan: UpgradeLab.sln
Hop: net6.0 to net10.0
SDK used: 10.0.402
Projects: 3 (3 surveyed; 0 under "Not checked")
Support/EOL check
- Fetched: https://learn.microsoft.com/en-us/dotnet/core/releases-and-support, read 2026-10-26.
- net6.0: absent from the currently-supported list; the build's own NETSDK1138 warning confirms out-of-support ("out of support and will not receive security updates"). No specific EOL date is carried on this page for net6.0, so none is asserted here.
- net10.0: LTS, supported until November 2028.
- Recommendation: net10.0 is already the nearest LTS — proceed with the proposed target rather than an intermediate hop.
Breaking changes found and confirmed
- BCL. BinaryFormatter migration guide, https://learn.microsoft.com/en-us/dotnet/standard/serialization/binaryformatter-migration-guide/, introduced in .NET 9: "we no longer include an implementation of BinaryFormatter in the runtime... their implementation always throws a PlatformNotSupportedException." Hit at
src/UpgradeLab.Api/LegacyExport.cs:12,20(2 occurrences). Throws at runtime on .NET 9+ today; becomes a hard compile error once the project itself targets net9.0+. - EF Core / Microsoft.Data.Sqlite. EF Core 10 breaking changes, https://learn.microsoft.com/en-us/ef/core/what-is-new/ef-core-10.0/breaking-changes, introduced in EF Core 10: "Writing DateTimeOffset into REAL column now writes in UTC." Hit at
src/UpgradeLab.Data/TimestampRoundTrip.cs:11,26(REAL column + GetFieldValue<DateTimeOffset>, 2 occurrences). Stored wall-clock hour shifts because the value is now normalized to UTC before writing. - ASP.NET Core. WithOpenApi deprecation (ASPDEPR002), https://aka.ms/aspnet/deprecate/002 → https://github.com/aspnet/Announcements/issues/519: "duplicated functionality now provided by the built-in OpenAPI document generation pipeline." Hit at
src/UpgradeLab.Api/Program.cs:17(1 occurrence). Obsolete now, scheduled for removal; replace with the built-in pipeline (AddOpenApiOperationTransformer) or drop the call.
Checked, not applicable
None in this run — every breaking-change candidate pulled from the fetched docs for this hop had a confirmed grep hit in this fixture.
Could not check
None — all three live doc fetches and both build/test cycles completed.
Package-version diff proposed
| Package | Current | Proposed | Reason |
|---|---|---|---|
| Microsoft.EntityFrameworkCore.Sqlite | not pinned in a lockfile the run could read | 10.0.14 | EF Core major version must track the net10.0 target; verified against the package's current listing, not assumed |
| Microsoft.AspNetCore.OpenApi | not referenced | 10.0.14 | Needed once WithOpenApi is replaced by the built-in OpenAPI pipeline on net10.0 |
Baseline test run (before)
dotnet test (declared net6.0; executed on .NET 10.0.13 — no net6.0-era ASP.NET Core shared framework is installed, so the host rolled forward): exit non-zero; 1 passed, 2 failed, 0 skipped. Log: baseline-test-rollforward-detail.log.
Writes made
UpgradeLab.Data.csproj,UpgradeLab.Api.csproj,UpgradeLab.Tests.csproj: TargetFramework net6.0 to net10.0.UpgradeLab.Data.csproj,UpgradeLab.Tests.csproj: Microsoft.EntityFrameworkCore.Sqlite bumped to 10.0.14.UpgradeLab.Api.csproj: Microsoft.AspNetCore.OpenApi 10.0.14 added.src/UpgradeLab.Api/LegacyExport.cs: BinaryFormatter calls replaced with System.Text.Json.src/UpgradeLab.Api/Program.cs:.WithOpenApi()call removed.
Build and test after the bump
dotnet build: exit 0; 0 warnings, 0 errors. dotnet test: exit 0; 3 passed, 0 failed, 0 skipped. Log: final-clean-build.log, final-clean-test.log.
Regressions
None. (The two baseline failures were the trigger conditions this hop was meant to surface and fix, not previously-passing tests that broke — see "Breaking changes found and confirmed.")
Not checked
- The exact pre-bump Microsoft.EntityFrameworkCore.Sqlite version: no version control in this fixture, so only the observed before/after behavior is reported, not a cited version number.
- Whether the repo-grep step would find an unfamiliar breaking change in a repo that wasn't built with known trigger locations.
- Other hops, other SDKs, Linux/macOS: not run in this session.
Connects securely to your tools. The creator never sees your data.
About this skill
Plans a .NET target-framework (TFM) bump for an existing solution and tells you, with citations, what the new TFM requires, what it breaks, what needs a version bump, and whether the test suite still passes.
The breaking-changes list is never hardcoded. Every run fetches Microsoft's current support-policy page and the current breaking-changes/migration docs for the specific hop you're making, and cites the URL, the section and a short quote for each one — because that list changes with every .NET release and a cached or remembered list goes stale.
Use when you want to plan, scope or validate moving a .NET project or solution to a newer TargetFramework, want to know what a TFM bump would break before you attempt it, or want the current .NET support/EOL status checked before committing to a target.
Do not use for general NuGet dependency updates that aren't tied to a target-framework change, a best-practice or analyzer audit of code that isn't about to move TFM (use the .NET Best Practice Checker or .NET Roslyn Analyzer Rollout), or non-.NET projects.
Why not a generic dependency-upgrade skill
Agensi already lists generic, language-agnostic dependency-upgrade skills. Those bump package versions across any ecosystem; none of them read Microsoft's live TFM support/EOL or breaking-changes docs, and none triage .NET-runtime, EF Core or ASP.NET Core breaking changes against what a repo actually uses. This skill does only that one job — the TFM hop itself, not general dependency hygiene.
How it works
- Survey, read-only, no dotnet, no network. Finds every
.sln/.slnx/.csproj, reads eachTargetFramework/TargetFrameworks,Directory.Build.props,Directory.Packages.propsandglobal.json. - Baseline test run, on approval. Builds and runs the existing suite on the current TFM before touching anything.
- Live support/EOL check. Fetches Microsoft's current support-policy page and flags a target that's at or near end of support, recommending the nearest LTS instead.
- Live breaking-changes fetch, then grep-confirm. Fetches the runtime/BCL, EF Core and ASP.NET Core breaking-changes docs for the hop, turns each candidate into a grep pattern, and keeps only the ones with a real hit in the repo.
- Package-version diff. Flags the NuGet packages that need to move with the new TFM, verifying each version rather than assuming EF Core/ASP.NET packages track the runtime's major version.
- Propose once, ask. Shows the exact diff and the confirmed breaking-change fixes together, and asks whether to apply all, part, or none.
- Write on approval, then build. Applies only what was approved, one bucket at a time, and builds.
- Rebuild and re-test, compare. Re-runs the same suite on the new TFM and reports any regression — never silently patched.
- Report, listing every write, every build/test run, every doc fetched and cited, and everything not run.
Rules it keeps
- Never hardcodes support dates or breaking changes — every claim is fetched live and cited (URL, date, short quote).
- A breaking change only makes the proposal if a grep hit and a read of the surrounding code confirm the repo actually uses it.
- Package-version bumps are verified against the package's own current listing, not assumed.
- The test gate runs before and after, both only on approval, and a regression is reported, never fixed by editing the test or the code under test.
- Everything not run is listed under "Not checked" with the reason, never folded into a "clean" result.
What is in the package
Markdown only, no scripts: SKILL.md, seven reference files (survey and scope, live support-policy check, breaking-change doc sources, usage triage, package-version diff, build-and-test gate, report template), and docs/VALIDATION.md with the recorded run and real build/test logs.
Known limitations
- Tuned and tested on one synthetic solution written for this purpose. Behavior on a large real solution, or on a hop this fixture didn't cover, is unverified.
- The repo-grep step is only shown confirming patterns at locations already known to exist; it hasn't been shown finding an unfamiliar breaking change in an unannotated repo.
- Live doc fetches depend on Microsoft's pages being reachable and unchanged in structure.
- No formal before/after test of every documented mitigation switch for a breaking change.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Code Quality & Review.
Requires dotnet CLI installed. Cannot verify breaking changes not found in official Microsoft online docs. One solution at a time. Does not perform general security-only package updates.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Free to use
No account required to browse
Trust & safety
Security scan
Security scan passed 21 days ago
- Free with an Agensi account