What inputs does ln-712-nuget-upgrader require?

A solution or project path; it discovers .csproj files and, if present, a .sln to drive upgrades.

Does it handle breaking changes automatically?

It detects breaking changes by comparing current vs latest major versions and consults migration patterns and MCP tools; upgrades may be blocked if critical issues are found, otherwise upgrades are applied with a migration report.

Which .NET versions are supported?

Supports .NET 6, 7, 8, 9, 10 as listed in the overview.

ln-712-nuget-upgrader

Scanned

npx machina-cli add skill levnikolaevich/claude-code-skills/ln-712-nuget-upgrader --openclaw

Files (1)

SKILL.md

5.8 KB

Paths: File paths (shared/, references/, ../ln-*) are relative to skills repo root. If not found at CWD, locate this SKILL.md directory and go up one level for repo root.

ln-712-nuget-upgrader

Type: L3 Worker Category: 7XX Project Bootstrap Parent: ln-710-dependency-upgrader

Upgrades .NET NuGet packages with automatic breaking change detection and migration.

Overview

Aspect	Details
Input	Solution/project path
Output	Updated .csproj files, migration report
Supports	.NET 6, 7, 8, 9, 10

Workflow

See diagram.html for visual workflow.

Phases: Pre-flight → Find Projects → Security Audit → Check Outdated → Identify Breaking → Apply Upgrades → Restore & Build → Report

Phase 0: Pre-flight Checks

Check	Required	Action if Missing
.csproj file(s)	Yes	Block upgrade
.sln file	No	Use csproj discovery instead

Workers assume coordinator (ln-710) already verified git state and created backup.

Phase 1: Find Projects

Discovery Methods

Method	Command
Find .csproj	`Get-ChildItem -Recurse -Filter *.csproj`
From solution	`dotnet sln list`

Phase 2: Security Audit

Commands

Check	Command
Vulnerable packages	`dotnet list package --vulnerable`
Outdated packages	`dotnet list package --outdated`

Actions

Severity	Action
Critical	Block upgrade, report
High	Warn, continue
Moderate/Low	Log only

Phase 3: Check Outdated

Using dotnet-outdated

Step	Command
Install tool	`dotnet tool install --global dotnet-outdated-tool`
Check	`dotnet outdated --output json`

Phase 4: Identify Breaking Changes

Detection

Compare current vs latest major versions
Check breaking_changes_patterns.md
Use MCP tools (see below) for migration guides

Common Breaking Changes

Package	Breaking Version	Key Changes
Microsoft.EntityFrameworkCore	8 → 9	Query changes, migration format
Serilog.AspNetCore	7 → 8	Configuration format
Swashbuckle.AspNetCore	6 → 7	Minimal API support

MCP Tools for Migration Search

Priority Order (Fallback Strategy)

Priority	Tool	When to Use
1	mcp__context7__query-docs	First choice for library docs
2	mcp__Ref__ref_search_documentation	Official Microsoft docs
3	WebSearch	Latest info, community solutions

Context7 Usage

Step	Tool	Parameters
1. Find library	mcp__context7__resolve-library-id	libraryName: "EntityFrameworkCore"
2. Query docs	mcp__context7__query-docs	query: "EF Core 8 to 9 migration breaking changes"

MCP Ref Usage

Action	Tool	Query Example
Search	mcp__Ref__ref_search_documentation	"dotnet EntityFrameworkCore 9 migration guide"
Read	mcp__Ref__ref_read_url	URL from search results

WebSearch Fallback

Use when Context7/Ref return no results:

"<package> .NET <version> breaking changes migration"
"<error code> <package> fix"

Phase 5: Apply Upgrades

Priority Order

Priority	Package Type
1	SDK/Runtime (Microsoft.NET.Sdk)
2	Framework (Microsoft.AspNetCore.*)
3	EF Core (affects migrations)
4	Logging (Serilog.*)
5	Other packages

Commands

Action	Command
Update specific	`dotnet add package <name> --version <ver>`
Update all	`dotnet outdated --upgrade`

Phase 6: Restore & Build

Commands

Step	Command
Restore	`dotnet restore`
Build	`dotnet build --configuration Release`
Test	`dotnet test`

On Failure

Identify failing package from error
Search Context7/Ref for migration guide
If unresolved: rollback package, continue

Phase 7: Report Results

Report Schema

Field	Description
solution	Solution path
projects[]	Updated projects
duration	Total time
upgrades[]	Applied upgrades
buildVerification	PASSED or FAILED
testResults	X passed, Y failed

Configuration

Options:
  # Upgrade scope
  upgradeType: major          # major | minor | patch

  # Security
  auditLevel: high
  minimumReleaseAge: 14

  # .NET specific
  includePrerelease: false
  targetFramework: net10.0

  # Verification
  runTests: true
  runBuild: true

Error Handling

Error	Cause	Solution
CS0246	Missing type	Search for replacement API
NU1605	Downgrade detected	Check package constraints
Build fail	Breaking change	Apply migration via Context7

References

Definition of Done

All .csproj files discovered (via solution or recursive scan)
Security audit completed (dotnet list package --vulnerable)
Outdated packages identified via dotnet-outdated
Breaking changes detected via breaking_changes_patterns.md and MCP tools
Upgrades applied in priority order (SDK > Framework > EF Core > other)
dotnet restore, dotnet build, dotnet test all pass
Report returned with projects updated, upgrades applied, and build/test status

Version: 1.1.0 Last Updated: 2026-01-10

Source

git clone https://github.com/levnikolaevich/claude-code-skills/blob/master/ln-712-nuget-upgrader/SKILL.mdView on GitHub

Overview

ln-712-nuget-upgrader upgrades .NET NuGet packages with automatic breaking change detection and migration. It analyzes your solution or project, flags outdated and vulnerable packages, and applies upgrades with migration guidance while producing a comprehensive migration report.

How This Skill Works

The workflow runs in phases: pre-flight checks for csproj/sln, project discovery, security audit and outdated checks, detection of breaking changes by comparing current vs latest major versions and consulting breaking_changes_patterns.md, then applies upgrades, runs restore and build, and outputs a migration report.

When to Use It

You maintain a .NET solution with multiple NuGet dependencies and need to upgrade to newer major versions.
A security audit shows vulnerable or outdated packages that require upgrading.
You must migrate EF Core or other libraries with documented breaking changes.
You want automated migration guidance from official docs before upgrading.
You need to update packages and verify the solution builds with restore and tests.

Quick Start

Step 1: Point the upgrader at your solution or project path and ensure a git backup.
Step 2: Run the upgrader to discover projects, run security/audit checks, and detect outdated packages.
Step 3: Review the migration report, apply upgrades, then run dotnet restore and build to validate.

Best Practices

Start with Phase 0 pre-flight checks: ensure at least one .csproj and run upgrades in a branch.
Keep git backups and coordinate with the repo owner as the skill notes.
Review the migration report and breaking-change notes before applying upgrades.
Prioritize upgrades in the order defined (SDK/Runtime, Framework, EF Core, logging, other).
Run dotnet restore and build to verify the upgrade after changes.

Example Use Cases

Upgrade EF Core from 8 to 9 and address new query and migration format changes using migration guides.
Migrate Serilog.AspNetCore from 7 to 8 and adjust configuration changes as documented.
Upgrade multiple NuGet packages identified by dotnet-outdated in a multi-project solution.
Upgrade Swashbuckle.AspNetCore with Minimal API support considerations.
Apply upgrades across shared/ and references/ folders in a multi-project repo, ensuring successful restore and build.

Frequently Asked Questions

Add this skill to your agents