nuget-manager

Manage NuGet packages across .NET projects using the dotnet CLI.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures consistent and safe NuGet package management across .NET projects by enforcing usage of the dotnet CLI for adding, removing, and updating packages, and by guiding a safe version-up workflow that avoids manual edits to project files.

Core Features & Use Cases

  • Enforce dotnet CLI for all package management actions to preserve project integrity.
  • Centralized version updates workflow: determine where versions are managed and update accordingly, followed by immediate dotnet restore.
  • Safe change validation: verify package versions exist in NuGet before applying changes and ensure restoration passes.

Quick Start

Use the NuGet Manager to add or update a package in your .NET solution using the dotnet CLI. Example tasks include adding a package, removing a package, or updating a package version with restoration as part of the process.

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 projects in a solution?

To update a NuGet package version across multiple projects, the dotnet CLI detects whether versions are managed centrally or per-project, applies the changes accordingly, and runs dotnet restore to ensure project integrity.

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

The safest way to manage NuGet packages in a .NET monorepo is by enforcing the dotnet CLI for all additions and removals, which prevents manual project file edits and maintains consistency across all projects.

How does dotnet restore validate NuGet package changes before applying them?

Dotnet restore validates changes by verifying that the specified package versions actually exist on NuGet before applying them, and then it confirms the restoration passes to ensure safe change validation.

Can I use this CLI-based NuGet management approach for centralized version control?

Yes, this approach supports centralized version control workflows by determining where package versions are managed and updating them accordingly, followed immediately by running dotnet restore to validate.

Why should I avoid manually editing csproj files for dependency management?

Manually editing csproj files for dependency management bypasses safe change validation, whereas enforcing the dotnet CLI verifies package versions exist on NuGet and ensures restoration passes to maintain project integrity.