Manage NuGet packages in .NET projects/solutions. Use this skill when adding, removing, or updating NuGet package versions. It enforces using `dotnet` CLI for package management and provides strict procedures for direct file edits only when updating versions.
Start a fresh conversation. Replace the highlighted placeholders.
Use nuget-manager to update [package name] to [target version] in [solution or project], verifying the version exists, respecting central versus per-project management, and running dotnet restore after the change.
Required inputs
[package name]
[target version]
[solution or project]
User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗
SKILL.md
name: nuget-managerdescription: 'Manage NuGet packages in .NET projects/solutions. Use this skill when adding, removing, or updating NuGet package versions. It enforces using `dotnet` CLI for package management and provides strict procedures for direct file edits only when updating versions.'
NuGet Manager
Overview
This skill ensures consistent and safe management of NuGet packages across .NET projects. It prioritizes using the dotnet CLI to maintain project integrity and enforces a strict verification and restoration workflow for version updates.
Prerequisites
.NET SDK installed (typically .NET 8.0 SDK or later, or a version compatible with the target solution).
dotnet CLI available on your PATH.
jq (JSON processor) OR PowerShell (for version verification using dotnet package search).
Core Rules
NEVER directly edit .csproj, .props, or Directory.Packages.props files to add or remove packages. Always use dotnet add package and dotnet remove package commands.
DIRECT EDITING is ONLY permitted for changing versions of existing packages.
VERSION UPDATES must follow the mandatory workflow:
Verify the target version exists on NuGet.
Determine if versions are managed per-project (.csproj) or centrally (Directory.Packages.props).
Update the version string in the appropriate file.
Immediately run dotnet restore to verify compatibility.
Verify Version Existence:
Check if the version exists using the dotnet package search command with exact match and JSON formatting.
Using jq:
dotnet package search <PACKAGE_NAME> --exact-match --format json | jq -e '.searchResult[].packages[] | select(.version == "<VERSION>")'
Using PowerShell:
(dotnet package search <PACKAGE_NAME> --exact-match --format json | ConvertFrom-Json).searchResult.packages | Where-Object { $_.version -eq "<VERSION>" }
Determine Version Management:
Search for Directory.Packages.props in the solution root. If present, versions should be managed there via <PackageVersion Include="Package.Name" Version="1.2.3" />.
If absent, check individual .csproj files for <PackageReference Include="Package.Name" Version="1.2.3" />.
Apply Changes:
Modify the identified file with the new version string.
Verify Stability:
Run dotnet restore on the project or solution. If errors occur, revert the change and investigate.