nuget-manager

Manage NuGet packages in .NET solutions using the dotnet CLI.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill provides a structured and safe way to manage NuGet packages in .NET projects, preventing common errors and ensuring project integrity.

Core Features & Use Cases

  • Add/Remove Packages: Uses dotnet add package and dotnet remove package for safe package management.
  • Update Versions: Guides through a strict process for updating package versions, including verification and restoration.
  • Centralized vs. Project Management: Identifies whether package versions are managed centrally in Directory.Packages.props or per-project in .csproj files.
  • Use Case: Quickly add a new logging library to your .NET solution or update a critical dependency to its latest stable version.

Quick Start

Use the nuget-manager skill to add the 'Newtonsoft.Json' package to the 'MyProject.csproj' file.

Frequently Asked Questions about nuget-manager

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

FAQPage Schema
How do I add or remove NuGet packages in a .NET project safely?

To manage NuGet packages safely, use the `dotnet add package` and `dotnet remove package` CLI commands. This enforces structured package management within your .NET solutions, preventing common errors and ensuring overall project integrity.

What is the best way to update NuGet package versions in a .NET solution?

The best way to update NuGet package versions is through a strict process using the `dotnet` CLI. This includes verifying the new version and restoring packages to ensure compatibility and maintain project stability throughout the dependency update.

Does this NuGet management approach work with centralized package versions?

Yes, this NuGet management approach works with centralized package versions. It identifies whether your package versions are managed centrally in `Directory.Packages.props` files or managed per-project within individual `.csproj` files.

Do I need the .NET SDK to manage NuGet dependencies?

Yes, the .NET SDK is required to manage NuGet dependencies because the process enforces the use of the `dotnet` CLI for all package operations. Optionally, `jq` or PowerShell can be used for version verification tasks.

Why use the dotnet CLI instead of editing csproj files directly for dependency management?

Using the `dotnet` CLI instead of editing `.csproj` files directly prevents common configuration errors during dependency management. It provides a structured and safe way to add, remove, and update packages while ensuring project stability.