nuget-manager

Manages NuGet package versions in .csproj or Directory.Packages.props files.

Updated Jan 14, 2026
One-click install
npx skills add https://github.com/webmaxru/octocat_supply --skill nuget-manager-webmaxru
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nuget-manager
Source: https://github.com/webmaxru/octocat_supply/tree/main/.github/skills/nuget-manager
Command: npx skills add https://github.com/webmaxru/octocat_supply --skill nuget-manager-webmaxru

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inconsistent or unsafe NuGet package changes can cause build failures, dependency drift, and runtime issues across .NET solutions, and this skill prescribes a repeatable, verified workflow to minimize those risks.

Core Features & Use Cases

  • Enforce safe operations: Require dotnet add/remove for adding or removing packages and restrict direct file edits to version updates only.
  • Version management detection: Detect whether versions are managed centrally via Directory.Packages.props or per-project in .csproj files and update the correct location.
  • Verification and restore: Verify target versions exist on NuGet, update the version string, and run dotnet restore to validate compatibility.
  • Use Case: Update Newtonsoft.Json to a specific version across a solution by locating its definition, updating the version, and confirming restore succeeds.

Quick Start

Use the nuget-manager skill to update a package version across the repository, verify the version exists on NuGet, apply the change in the appropriate file, and run dotnet restore to confirm compatibility.

Frequently Asked Questions about nuget-manager

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

FAQPage Schema
How do I update a NuGet package version across multiple .NET projects in a solution?

To update a NuGet package version across .NET projects, this skill detects whether versions are centralized in Directory.Packages.props or managed per-project in csproj files, updates the correct location, and runs dotnet restore to verify compatibility.

What is the safest way to add or remove NuGet packages in a .NET repository?

The safest way to add or remove NuGet packages is using the dotnet add and dotnet remove commands rather than direct file edits, which this workflow enforces to prevent build failures and dependency drift across the .NET solution.

When do I need to use Directory.Packages.props for NuGet package management?

You need to use Directory.Packages.props for NuGet package management when centralizing versions across a .NET repository, which this skill automatically detects to ensure consistent dependency updates and avoid version conflicts.

Do I need the .NET SDK and dotnet CLI installed to manage NuGet package versions?

Yes, you need the .NET SDK and the dotnet CLI installed to manage NuGet package versions, as this skill requires them to search for target versions on NuGet, apply changes, and run dotnet restore for validation.

Why should I run dotnet restore after changing a package version in csproj files?

You should run dotnet restore after changing a package version in csproj files to validate that the specified version exists on NuGet and is compatible with your project, preventing runtime issues and build failures from invalid dependencies.

Can I directly edit csproj files to change NuGet package versions?

Direct file edits in csproj files should be restricted to version updates only, while adding or removing packages requires dotnet CLI commands, ensuring safe NuGet operations and verified compatibility through dotnet restore.