nuget-manager

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

37.6k|4.7k|Updated Jun 11, 2025
One-click install
npx skills add https://github.com/github/awesome-copilot --skill nuget-manager
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nuget-manager
Source: https://github.com/github/awesome-copilot/tree/main/skills/nuget-manager
Command: npx skills add https://github.com/github/awesome-copilot --skill nuget-manager

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enforces safe NuGet package management across .NET projects by guiding and automating changes through the dotnet CLI, preventing risky direct edits to project files and ensuring consistent workflows.

Core Features & Use Cases

  • DOTNET CLI workflows: Use dotnet add and dotnet remove to manage packages without manual edits.
  • Version-update discipline: Follow a strict workflow to verify versions exist, determine central or per-project version management, update the correct file, and run dotnet restore.
  • Use Case: Update a package across multiple projects in a solution or align all projects to a central Directory.Packages.props file.

Quick Start

Use the nuget-manager to add a package to a project: dotnet add src/MyProject/MyProject.csproj package Newtonsoft.Json

Frequently Asked Questions about nuget-manager

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

FAQPage Schema
How do I safely add or remove NuGet packages from my .NET project?

Use dotnet add and dotnet remove commands through the dotnet CLI to manage NuGet packages safely without manual edits to project files. This enforces consistent workflows and prevents errors from direct file manipulation.

Can I update NuGet packages across multiple projects in a solution at once?

Yes, NuGet package management supports both per-project and centralized version management via Directory.Packages.props. The workflow identifies your setup, applies updates to the correct file, and runs dotnet restore to verify compatibility.

How do I verify a NuGet package version exists before updating it?

The package management workflow checks that target versions exist on NuGet before applying changes, preventing failed restores and ensuring all projects remain compatible after updates.

What's the difference between per-project and centralized NuGet version management?

Per-project management stores versions in individual .csproj files; centralized management uses Directory.Packages.props to align versions across a solution. The dotnet CLI workflow automatically detects and updates the correct location.

Do I need to run dotnet restore after updating packages?

Yes, dotnet restore is run automatically after package updates to ensure all dependencies resolve correctly and projects remain in a compatible state across your solution.

Can this approach work with solutions containing multiple projects?

Yes, the NuGet management workflow applies across solutions and projects, supporting both adding packages to individual projects and updating versions consistently when using centralized version management.