nuget-manager

Automates NuGet package management for .NET projects via dotnet CLI workflows.

1|1|Updated Jun 4, 2024
One-click install
npx skills add https://github.com/dhar174/tiny_village --skill nuget-manager-dhar174
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nuget-manager
Source: https://github.com/dhar174/tiny_village/tree/main/.github/skills/nuget-manager
Command: npx skills add https://github.com/dhar174/tiny_village --skill nuget-manager-dhar174

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

NuGet package management in .NET projects can be error-prone when updates are performed manually across multiple project files. This skill enforces a safe, consistent workflow using the dotnet CLI to add, remove, and update packages while preventing unsafe direct edits to versioned files and ensuring successful restoration.

Core Features & Use Cases

  • Add, update, and remove packages via dotnet CLI to maintain project integrity.
  • Detect whether versions are managed per-project (.csproj) or centrally (Directory.Packages.props) and apply changes accordingly.
  • Verify the target version exists on NuGet and perform a dotnet restore to confirm compatibility.
  • Use Case: Update a critical library across a multi-project solution without breaking builds.

Quick Start

Add a package to a target project using the dotnet CLI and verify restoration.

Frequently Asked Questions about nuget-manager

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

FAQPage Schema
How do I update NuGet packages across a multi-project .NET solution without breaking builds?

To update NuGet packages safely, this skill uses the dotnet CLI to add, remove, or update packages across your .NET solution and runs dotnet restore to confirm compatibility and prevent build breaks.

When should I use Directory.Packages.props instead of editing .csproj files for NuGet package management?

You should use Directory.Packages.props for centralized version management instead of per-project .csproj files; the skill detects your current configuration and applies updates to the appropriate file automatically.

Can I verify a specific NuGet package version exists before adding it to my dotnet project?

Yes, you can verify a specific NuGet package version exists because the skill checks the target version on NuGet before applying any changes to your .csproj or Directory.Packages.props files.

What is the safest way to add or remove NuGet dependencies using dotnet CLI?

The safest way to add or remove NuGet dependencies is by using dotnet CLI workflows that prevent unsafe direct edits to versioned files and perform a dotnet restore to ensure project integrity.

Does manual NuGet package versioning in .csproj files cause restore errors?

Manual NuGet package versioning in .csproj files can cause restore errors from inconsistent updates; enforcing dotnet CLI workflows and verifying versions on NuGet prevents these compatibility issues.