nuget-manager

Automate NuGet package management and conflict resolution for C# projects.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/kongliuli/VibeSkills --skill nuget-manager-kongliuli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nuget-manager
Source: https://github.com/kongliuli/VibeSkills/tree/main/Skills/C%23/common/nuget-manager
Command: npx skills add https://github.com/kongliuli/VibeSkills --skill nuget-manager-kongliuli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

C# projects often face tangled NuGet dependencies, conflicting versions, and scattered package configurations. This Skill provides a centralized approach to manage dependencies, enforce version constraints, configure PackageReference, and handle private NuGet sources to keep projects clean and conflict-free.

Core Features & Use Cases

  • Dependency management: centralize and audit NuGet package usage across multi-project solutions.
  • Version constraint strategy: define and apply consistent version ranges to prevent conflicts.
  • PackageReference configuration: streamline project file configuration and sharing of common settings.
  • Private NuGet sources: configure and secure private feeds for internal packages.
  • Conflict resolution: detect and resolve package version clashes to ensure successful builds.
  • Use Case: Maintaining a suite of C# projects, ensuring all packages stay aligned and up to date.

Quick Start

Navigate to your C# solution directory and perform the following steps:

  • Ensure the .NET SDK is installed and accessible via the command line.
  • Use dotnet add package to introduce a package (e.g., dotnet add package Newtonsoft.Json --version 13.0.3).
  • Configure a NuGet.config file to include both public and private feeds.
  • Align versions using a central props or Directory.Build.props with PackageVersion entries and reference them in your projects.

Frequently Asked Questions about nuget-manager

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

FAQPage Schema
How do I resolve NuGet package version conflicts across multiple C# projects?

You can resolve NuGet package version conflicts by centralizing dependency management with a Directory.Build.props file to define PackageVersion entries, ensuring all projects reference consistent versions and prevent clashes.

What is the best way to enforce consistent NuGet version constraints in a multi-project solution?

The best way to enforce NuGet version constraints is by defining consistent version ranges in a central props file. This strategy applies uniform package references across the entire multi-project solution to prevent dependency mismatches.

How do I configure private NuGet feeds for internal packages?

You configure private NuGet feeds by setting up a NuGet.config file that includes both public and private sources. This secures access to internal packages while maintaining standard public feed dependencies.

Does NuGet PackageReference configuration support sharing common settings across projects?

Yes, PackageReference configuration supports sharing common settings across projects. By streamlining project file configurations and using central props files, you can efficiently manage and distribute shared package settings.

Why do I need a central props file for NuGet dependency management?

You need a central props file for NuGet dependency management to audit and centralize package usage across multi-project solutions. This approach prevents scattered configurations and ensures version alignment to guarantee successful builds.

What is required to start automating NuGet package management for C# projects?

To start automating NuGet package management, you need the .NET SDK installed and accessible via the command line. You then use dotnet add package commands and configure a NuGet.config file for dependency sources.