Nuget Manager

1---2name: nuget-manager3description: 'Manage NuGet packages in .NET projects/solutions. Use this skill when adding, removing, or updating NuGet package versions. It enforces using `dotnet` CLI for package management and provides strict procedures for direct file edits only when updating versions.'4---5 6# NuGet Manager7 8## Overview9 10This skill ensures consistent and safe management of NuGet packages across .NET projects. It prioritizes using the `dotnet` CLI to maintain project integrity and enforces a strict verification and restoration workflow for version updates.11 12## Prerequisites13 14- .NET SDK installed (typically .NET 8.0 SDK or later, or a version compatible with the target solution).15- `dotnet` CLI available on your `PATH`.16- `jq` (JSON processor) OR PowerShell (for version verification using `dotnet package search`).17 18## Core Rules19 201.  **NEVER** directly edit `.csproj`, `.props`, or `Directory.Packages.props` files to **add** or **remove** packages. Always use `dotnet add package` and `dotnet remove package` commands.212.  **DIRECT EDITING** is ONLY permitted for **changing versions** of existing packages.223.  **VERSION UPDATES** must follow the mandatory workflow:23    - Verify the target version exists on NuGet.24    - Determine if versions are managed per-project (`.csproj`) or centrally (`Directory.Packages.props`).25    - Update the version string in the appropriate file.26    - Immediately run `dotnet restore` to verify compatibility.27 28## Workflows29 30### Adding a Package31Use `dotnet add [<PROJECT>] package <PACKAGE_NAME> [--version <VERSION>]`.32Example: `dotnet add src/MyProject/MyProject.csproj package Newtonsoft.Json`33 34### Removing a Package35Use `dotnet remove [<PROJECT>] package <PACKAGE_NAME>`.36Example: `dotnet remove src/MyProject/MyProject.csproj package Newtonsoft.Json`37 38### Updating Package Versions39When updating a version, follow these steps:40 411.  **Verify Version Existence**:42    Check if the version exists using the `dotnet package search` command with exact match and JSON formatting. 43    Using `jq`:44    `dotnet package search <PACKAGE_NAME> --exact-match --format json | jq -e '.searchResult[].packages[] | select(.version == "<VERSION>")'`45    Using PowerShell:46    `(dotnet package search <PACKAGE_NAME> --exact-match --format json | ConvertFrom-Json).searchResult.packages | Where-Object { $_.version -eq "<VERSION>" }`47    482.  **Determine Version Management**:49    - Search for `Directory.Packages.props` in the solution root. If present, versions should be managed there via `<PackageVersion Include="Package.Name" Version="1.2.3" />`.50    - If absent, check individual `.csproj` files for `<PackageReference Include="Package.Name" Version="1.2.3" />`.51 523.  **Apply Changes**:53    Modify the identified file with the new version string.54 554.  **Verify Stability**:56    Run `dotnet restore` on the project or solution. If errors occur, revert the change and investigate.57 58## Examples59 60### User: "Add Serilog to the WebApi project"61**Action**: Execute `dotnet add src/WebApi/WebApi.csproj package Serilog`.62 63### User: "Update Newtonsoft.Json to 13.0.3 in the whole solution"64**Action**:651. Verify 13.0.3 exists: `dotnet package search Newtonsoft.Json --exact-match --format json` (and parse output to confirm "13.0.3" is present).662. Find where it's defined (e.g., `Directory.Packages.props`).673. Edit the file to update the version.684. Run `dotnet restore`.