Overview
.NET NuGet Update treats dependency maintenance as an audited repository change, not a sequence of ad hoc version bumps. It inventories every declaration first, resolves safe candidates in batches, preserves conditional package graphs, and applies only minimal XML edits to the exact declarations that changed.
The workflow supports both central package management and project-owned PackageReference versions. Normal mode auto-applies revision, patch, minor, and same-major prerelease moves while batching major upgrades for one approval decision. Yolo mode keeps the same safety rules but skips the approval pause and reports held majors at the end.
Concepts
- Audit first, update second: the dependency audit is the work list, and every declaration must end in exactly one summary bucket before the run is complete.
- TFM-band safety: conditional central-package pins stay inside their declared framework band when the pinned package major matches that band.
- Intent-aware versioning: stable pins prefer stable candidates, prerelease pins allow prerelease movement, and major upgrades remain explicit approval decisions.
- Structural edits only: package files keep their existing conditions, comments, ordering, indentation, and line endings while only the targeted version value changes.
Installation
npx skills add https://github.com/codebeltnet/agentic --skill dotnet-nuget-update
Usage guidance
Use this skill when a .NET repository needs a dependency audit, a controlled update pass, or a grounded answer about outdated packages. Point it at the repository root and let it classify the entire package graph before touching any props or project files.
Choose normal mode when you want safe updates applied automatically but still want one approval checkpoint for majors. Choose dotnet-nuget-update yolo when you want the same audit and safe-update policy without the approval pause, while still holding major upgrades, note-bearing pins, unresolved packages, and conflicts for review.