nuget-manager

Automate NuGet package management in .NET projects using the dotnet CLI.

1|Updated Jan 30, 2023
One-click install
npx skills add https://github.com/ncksol/ravebot --skill nuget-manager-ncksol
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nuget-manager
Source: https://github.com/ncksol/ravebot/tree/main/.github/skills/nuget-manager
Command: npx skills add https://github.com/ncksol/ravebot --skill nuget-manager-ncksol

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

NuGet dependency management in .NET projects is error-prone when handled manually; this skill standardizes package updates, enforces the use of the dotnet CLI, and prevents risky direct edits to project files, reducing breakages and drift across solutions.

Core Features & Use Cases

  • Enforce using dotnet add package and dotnet remove package for all modifications to package references; direct edits to .csproj, .props, or Directory.Packages.props are avoided.
  • Detect whether versions are managed per-project or centrally, and update the appropriate file accordingly, followed by an automatic dotnet restore to validate compatibility.
  • Verify target versions exist on NuGet before applying changes and provide clear guidance for rollback if restoration fails.

Quick Start

Update a NuGet package to a specific version using dotnet add package and verify compatibility with dotnet restore.

Frequently Asked Questions about nuget-manager

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

FAQPage Schema
How do I safely update NuGet package versions across a .NET solution?

Safe NuGet package updates are automated using the dotnet CLI to add or remove packages, followed by an automatic dotnet restore to validate compatibility and prevent breakages across the solution.

Can I use dotnet CLI to manage centralized package versions in Directory.Packages.props?

Yes, the skill detects whether versions are managed per-project or centrally in Directory.Packages.props, applies changes to the correct file using dotnet CLI commands, and avoids risky direct edits.

What is the best way to prevent direct edits to csproj when adding NuGet dependencies?

The best way to prevent direct csproj edits is enforcing strict use of dotnet add package and dotnet remove package commands, standardizing modifications and reducing configuration drift across .NET solutions.

Why does dotnet restore fail after a manual NuGet package version change?

Manual NuGet package version changes often fail dotnet restore due to non-existent versions or incompatibilities; verifying package existence on NuGet before applying changes prevents restoration failures.

Does this approach work for rolling back a failed NuGet package update?

Yes, if dotnet restore fails after an update, the skill provides clear guidance for rollback, ensuring the .NET project returns to a stable and compatible package reference state.

Do I need to manually build my .NET project after updating NuGet packages?

No, manual builds are unnecessary after updating NuGet packages because the skill automatically performs builds and dotnet restore commands to verify compatibility and validate the applied changes.