Manage NuGet packages across .NET projects using the dotnet CLI.
npx skills add https://github.com/beel-collab/presets.dev --skill nuget-manager-beel-collab
Please help me install this Agent Skill. Skill: nuget-manager Source: https://github.com/beel-collab/presets.dev/tree/main/skills/nuget-manager Command: npx skills add https://github.com/beel-collab/presets.dev --skill nuget-manager-beel-collab
This skill ensures consistent and safe management of NuGet packages across .NET projects by enforcing the dotnet CLI workflow for adding, removing, and updating packages.
Use the nuget-manager skill to add or update a package, for example: dotnet add src/MyProject/MyProject.csproj package Newtonsoft.Json --version 13.0.3
High-intent search queries and answers about installing and using this skill.
To update NuGet package versions consistently across multiple .NET projects, use the dotnet CLI for all add, remove, and version-update operations. This enforces a strict verification and restoration workflow, localizing changes to either per-project csproj files or centrally via Directory.Packages.props.
The best way to add a NuGet package without directly editing csproj files is using the dotnet add package command. This CLI-driven approach verifies package existence on NuGet, applies changes to the correct file, and executes dotnet restore to validate the solution.
Yes, this NuGet management approach works with centralized Directory.Packages.props. It automatically localizes version management to either per-project csproj files or centrally via Directory.Packages.props, depending on your solution setup.
You should use the dotnet CLI to manage package versions because direct editing is limited to changing existing versions. The CLI enforces a safe workflow by verifying package existence on NuGet, applying changes to the correct file, and executing dotnet restore to validate compatibility.
To verify NuGet package compatibility after updating versions in a multi-project solution, execute dotnet restore. This validation step ensures the applied package changes do not break the solution's dependencies.
You need to use dotnet restore immediately after removing a package from a .NET project to validate the solution. Executing dotnet restore ensures the removal does not break existing dependencies and confirms overall compatibility.
jsamuelsen11Enforce .NET project conventions across multi-project solutions.
ncksolAutomate NuGet package management in .NET projects using the dotnet CLI.
MudraMartinManage NuGet package versions centrally using dotnet CLI commands.
Was85Manage NuGet packages in .NET projects using the dotnet CLI.
