Verified:GitHub

package-management

Manage NuGet packages across a solution using the dotnet CLI and Central Package Management.

Updated Feb 10, 2026

Search Tags:#cli #dotnet #nuget #package-management #dependency-management #project-configuration #central-package-management

Ready to run

npx skills add https://github.com/tientt010/Dotnet-JiraLite-Microservices --skill package-management-tientt010

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: package-management
Source: https://github.com/tientt010/Dotnet-JiraLite-Microservices/tree/main/.github/skills/package-management
Command: npx skills add https://github.com/tientt010/Dotnet-JiraLite-Microservices --skill package-management-tientt010

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams manage NuGet packages across a solution by enforcing CLI-based package operations, CPM centralization, and shared version variables to avoid manual XML edits.

Core Features & Use Cases

Central Package Management (CPM) to unify package versions across projects.
CLI commands: dotnet add/remove/list/restore for packages and CPM configuration.
Recommendations to avoid manual XML edits and manage transitive dependencies.

Quick Start

Update package references across the solution using the dotnet CLI to ensure consistency.

Frequently Asked Questions about package-management

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

FAQPage Schema

What is Central Package Management in .NET and how does it unify NuGet versions?▼

Central Package Management (CPM) unifies NuGet package versions across a solution by using a Directory.Packages.props file at the solution root. This prevents manual XML edits and ensures consistent dependency versions across multiple projects.

How do I add or update NuGet packages across multiple projects using the dotnet CLI?▼

You can add, remove, or update NuGet packages across projects using dotnet CLI commands. This approach enforces CLI-based package operations and maintains shared version variables within your Directory.Packages.props file to ensure solution-wide consistency.

Does Central Package Management require a specific file structure to work?▼

Yes, Central Package Management requires a Directory.Packages.props file at your solution root. You also need the dotnet tooling installed to perform package operations and apply CPM configurations across your solution projects.

Why should I use the dotnet CLI for NuGet management instead of editing project files manually?▼

Using the dotnet CLI for NuGet management avoids manual XML edits, reduces configuration errors, and streamlines operations like adding, removing, or restoring packages. It enforces shared version variables to maintain consistency across your entire solution.

Can I manage transitive dependencies using Central Package Management?▼

Yes, Central Package Management helps manage transitive dependencies by centralizing version control in the Directory.Packages.props file. The dotnet CLI executes package operations while CPM maintains shared versions to keep transitive dependencies consistent.

What are the limitations of using Central Package Management for NuGet packages?▼

Central Package Management requires a solution root with Directory.Packages.props and depends on the dotnet tooling for package operations. It is designed for solution-wide version centralization and may not suit workflows relying on isolated, project-specific package versioning.