skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
levnikolaevich/claude-code-skills220 installs

ln-822-nuget-upgrader

Upgrades .NET NuGet packages with breaking change handling. Use when updating .NET dependencies.

How do I install this agent skill?

npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-822-nuget-upgrader
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    The skill automates NuGet package upgrades for .NET projects. It uses official .NET CLI commands to audit, update, and verify project dependencies. It includes standard development workflows such as installing auxiliary tools from the NuGet registry and fetching project-specific configuration from the author's GitHub repository.

  • Socketpass

    No alerts

  • Snykwarn

    Risk: MEDIUM · 2 issues

  • Runlayerpass

    2 files scanned · No issues

What does this agent skill do?

Paths: File paths (references/, ../ln-*) are relative to this skill directory.

ln-822-nuget-upgrader

Type: L3 Worker Category: 8XX Optimization

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


Overview

AspectDetails
InputSolution or project path plus upgrade policy
OutputUpdated .csproj files and a machine-readable dependency upgrade summary
Supports.NET 6, 7, 8, 9, 10

Workflow

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


Phase 0: Pre-flight Checks

CheckRequiredAction if Missing
.csproj file(s)YesBlock upgrade
.sln fileNoFall back to recursive project discovery
dotnet CLIYesBlock upgrade
Workspace baseline safeYesIn managed runs coordinator already prepared it; in standalone runs protect rollback locally

Runtime Coordination

Managed runs receive deterministic runId and exact summaryArtifactPath from ln-820. Standalone runs remain supported; if runtime arguments are omitted, generate a standalone run-scoped artifact before returning.


Phase 1: Find Projects

MethodCommand
Find .csproj filesGet-ChildItem -Recurse -Filter *.csproj
Read solution membersdotnet sln list

Phase 2: Security Audit

CheckCommand
Vulnerable packagesdotnet list package --vulnerable
Outdated packagesdotnet list package --outdated

Actions:

SeverityAction
CriticalBlock and report
HighWarn and continue
Moderate/LowLog only

Phase 3: Check Outdated

StepCommand
Install helperdotnet tool install --global dotnet-outdated-tool
Detect outdated packagesdotnet outdated --output json

Phase 4: Identify Breaking Changes

Detection flow:

  1. Compare current vs latest major versions.
  2. Check breaking_changes_patterns.md.
  3. Use MCP tools for migration guides before changing code.

Common examples:

PackageBreaking VersionKey Changes
Microsoft.EntityFrameworkCore8 -> 9Query and migration changes
Serilog.AspNetCore7 -> 8Configuration updates
Swashbuckle.AspNetCore6 -> 7Minimal API integration changes

MCP Tools for Migration Search

PriorityToolWhen to Use
1mcp__context7__query-docsFirst choice for library docs
2mcp__Ref__ref_search_documentationOfficial Microsoft docs
3WebSearchLatest info and community fixes

Use the tool chain to confirm migrations before applying them.


Phase 5: Apply Upgrades

Priority order:

  1. SDK or runtime packages
  2. framework packages
  3. EF Core
  4. logging packages
  5. everything else
ActionCommand
Update one packagedotnet add package <name> --version <ver>
Update many packagesdotnet outdated --upgrade

Phase 6: Restore and Build

StepCommand
Restoredotnet restore
Builddotnet build --configuration Release
Testdotnet test

On failure:

  1. Identify the failing package.
  2. Search Context7 or Ref for the migration guide.
  3. If unresolved, rollback that package and continue.

Phase 7: Report Results

FieldDescription
solutionSolution path
projects[]Updated projects
durationTotal time
upgrades[]Applied upgrades
verificationRestore/build/test verdict
warnings[]Non-blocking issues
artifact_pathDurable worker report path, if written

Configuration

Options:
  upgradeType: major          # major | minor | patch
  auditLevel: high
  minimumReleaseAge: 14
  includePrerelease: false
  targetFramework: net10.0
  runTests: true
  runBuild: true

Error Handling

ErrorCauseSolution
CS0246Missing typeSearch for replacement API
NU1605Downgrade detectedCheck package constraints
Build failBreaking changeApply migration guide or rollback offending package

References


Runtime Summary Artifact

MANDATORY READ: Load references/coordinator_summary_contract.md

Emit a dependency-worker summary envelope.

Managed mode:

  • ln-820 passes deterministic runId and exact summaryArtifactPath
  • write the summary to the provided summaryArtifactPath

Standalone mode:

  • omit runId and summaryArtifactPath
  • write .hex-skills/runtime-artifacts/runs/{run_id}/dependency-worker/ln-822--{identifier}.json

Monitor (2.1.98+): For restore/build/test commands expected >30s, use Monitor. Fallback: Bash(run_in_background=true).

Definition of Done

  • All target .csproj files discovered
  • Security audit completed for NuGet dependencies
  • Outdated packages identified
  • Breaking changes checked via patterns plus current docs
  • Upgrades applied in a safe order with rollback on failure
  • dotnet restore, dotnet build, and required tests succeed
  • dependency-worker summary artifact written to the managed or standalone path

Version: 1.1.0 Last Updated: 2026-01-10

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/levnikolaevich/claude-code-skills/ln-822-nuget-upgrader">View ln-822-nuget-upgrader on skillZs</a>