nuget-manager

Manage .NET packages via CLI with automatic dependency resolution and validation.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/lzc0901/vibe_coding_template --skill nuget-manager-lzc0901
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nuget-manager
Source: https://github.com/lzc0901/vibe_coding_template/tree/main/skills/development-tools/nuget-manager
Command: npx skills add https://github.com/lzc0901/vibe_coding_template --skill nuget-manager-lzc0901

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures consistent and safe NuGet package management across .NET projects by enforcing the use of the dotnet CLI for add, remove, and update operations, preventing ad-hoc edits that could destabilize builds.

Core Features & Use Cases

  • Enforces using dotnet add package and dotnet remove package for package management.
  • Validates target versions exist on NuGet and determines whether versions are managed per-project or centrally.
  • Provides a repeatable workflow for updating package versions followed by immediate dotnet restore to verify compatibility.

Quick Start

Use the NuGet Manager to add or update a package via the dotnet CLI. Example: dotnet add <PROJECT_PATH> package Newtonsoft.Json --version 13.0.3

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 update a NuGet package in a .NET project using the dotnet CLI?

To safely add or update a NuGet package, use the dotnet CLI to apply changes and immediately run dotnet restore to verify version compatibility and build stability.

What is the best way to manage NuGet package versions across a multi-project .NET solution?

Managing NuGet package versions across multi-project solutions involves determining whether versions are centrally managed in Directory.Packages.props or handled in individual csproj files.

How does centralized NuGet package management work with Directory.Packages.props?

Centralized NuGet package management uses Directory.Packages.props to define versions once, and the dotnet CLI applies package changes to this correct file rather than individual csproj files.

Why should I use dotnet CLI commands instead of manually editing csproj files for package management?

Using dotnet CLI commands instead of manually editing csproj files prevents ad-hoc edits that could destabilize builds, ensuring all package changes are validated and restored immediately.

How do I verify if a specific NuGet package version exists before updating my .NET project?

You can verify if a target NuGet package version exists by checking the NuGet repository before applying changes, which the management workflow enforces to ensure version availability.

Can I use this dotnet CLI workflow to remove packages from per-project dependencies without breaking the build?

Yes, using dotnet remove package for per-project dependencies ensures safe removal, and running dotnet restore immediately after confirms that the build stability is maintained.