From dotnet
Manages NuGet packages in .NET projects using dotnet CLI for adding/removing and verified direct edits for version updates with restore checks.
npx claudepluginhub atc-net/atc-agentic-toolkit --plugin dotnetThis skill uses the workspace's default tool permissions.
This 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.
Manages NuGet packages in .NET projects using dotnet CLI commands and Central Package Management (CPM). Centralizes versions in Directory.Packages.props with shared variables, avoiding direct XML edits.
Interactively upgrades NuGet packages in .NET projects, detecting vulnerabilities, categorizing version changes, and warning about breaking changes or incompatibilities.
Provides .NET solution structure conventions with .slnx format, Directory.Build.props for shared properties, Directory.Packages.props for central package management, global usings, src/tests layout, and naming rules. Use for new solutions or project reconfiguration.
Share bugs, ideas, or general feedback.
This 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.
dotnet CLI available on your PATH.jq (JSON processor) OR PowerShell (for version verification using dotnet package search)..csproj, .props, or Directory.Packages.props files to add or remove packages. Always use dotnet add package and dotnet remove package commands..csproj) or centrally (Directory.Packages.props).dotnet restore to verify compatibility.Use dotnet add [<PROJECT>] package <PACKAGE_NAME> [--version <VERSION>].
Example: dotnet add src/MyProject/MyProject.csproj package Newtonsoft.Json
Use dotnet remove [<PROJECT>] package <PACKAGE_NAME>.
Example: dotnet remove src/MyProject/MyProject.csproj package Newtonsoft.Json
When updating a version, follow these steps:
Verify Version Existence:
Check if the version exists using the dotnet package search command with exact match and JSON formatting.
Using jq:
dotnet package search <PACKAGE_NAME> --exact-match --format json | jq -e '.searchResult[].packages[] | select(.version == "<VERSION>")'
Using PowerShell:
(dotnet package search <PACKAGE_NAME> --exact-match --format json | ConvertFrom-Json).searchResult.packages | Where-Object { $_.version -eq "<VERSION>" }
Determine Version Management:
Directory.Packages.props in the solution root. If present, versions should be managed there via <PackageVersion Include="Package.Name" Version="1.2.3" />..csproj files for <PackageReference Include="Package.Name" Version="1.2.3" />.Apply Changes: Modify the identified file with the new version string.
Verify Stability:
Run dotnet restore on the project or solution. If errors occur, revert the change and investigate.
Action: Execute dotnet add src/WebApi/WebApi.csproj package Serilog.
Action:
dotnet package search Newtonsoft.Json --exact-match --format json (and parse output to confirm "13.0.3" is present).Directory.Packages.props).dotnet restore.