Manage NuGet packages across .NET projects using the dotnet CLI.
npx skills add https://github.com/tfsugjp/csharptemplate --skill nuget-manager-tfsugjp
Please help me install this Agent Skill. Skill: nuget-manager Source: https://github.com/tfsugjp/csharptemplate/tree/main/.github/skills/nuget-manager Command: npx skills add https://github.com/tfsugjp/csharptemplate --skill nuget-manager-tfsugjp
Manage NuGet packages across .NET projects and solutions with safe, CLI-driven workflows. It prevents unsafe edits to project files and centralizes version management when possible to maintain build integrity.
Update a package version across the solution using the dotnet CLI and the appropriate centralized or per-project workflow.
High-intent search queries and answers about installing and using this skill.
To update a NuGet package version across a .NET solution, this Skill enforces a strict workflow using the dotnet CLI. It verifies package availability on NuGet, applies the update via centralized Directory.Packages.props or per-project csproj files, and validates a successful restore.
The safest way to manage NuGet packages is by using the dotnet CLI commands, specifically dotnet add package and dotnet remove package. This Skill prevents unsafe manual edits to project files and enforces a controlled restore workflow to maintain build integrity.
Yes, centralized NuGet version management is fully supported. This Skill detects whether your .NET projects use Directory.Packages.props for centralized control or per-project csproj files, applying the appropriate dotnet CLI workflow for your specific configuration.
You should use the dotnet CLI instead of directly editing csproj files to prevent unsafe modifications and maintain build integrity. This Skill automates safe add, remove, and update operations while validating package availability and ensuring a successful restore.
Yes, the dotnet CLI is required to manage NuGet packages with this Skill. It relies entirely on dotnet commands for adding, removing, and updating packages, and optionally uses dotnet package search to verify version availability before applying changes.
The main limitation is its strict dependency on the dotnet CLI and specific .NET project structures like Directory.Packages.props or csproj files. It does not support manual project file editing and mandates a controlled restore workflow, which may restrict custom package management scripts.
microcksManage NuGet packages in .NET projects via dotnet CLI commands.
rudironsoniConfigure GitHub Actions workflows for .NET build and test processes.
s205109Verify .NET solution builds, tests, formatting, and git status before commits.
MudraMartinManage NuGet package versions centrally using dotnet CLI commands.
