schedule-package-update

Updates outdated NuGet packages in .NET solutions and opens a pull request with verified changes.

Updated Sep 2, 2026
One-click install
npx skills add https://github.com/JSdotNet/devbook --skill schedule-package-update-jsdotnet
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: schedule-package-update
Source: https://github.com/JSdotNet/devbook/tree/main/plugins/delivery-schedule/skills/schedule-package-update
Command: npx skills add https://github.com/JSdotNet/devbook --skill schedule-package-update-jsdotnet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping NuGet dependencies current in a .NET solution is repetitive and error-prone: packages drift out of date, Central Package Management files need manual edits, and upgrades can silently break builds. This Skill automates the full audit-update-verify-PR cycle so dependency debt stays low without manual toil. ## Core Features & Use Cases - Outdated Package Audit: Runs dotnet list package --outdated, distinguishes centrally managed packages in Directory.Packages.props from per-project references, and presents an audit table with update type (patch, minor, major). - Safe Update Application: Applies minor and patch bumps by default, requires explicit confirmation for major versions, and reverts any package that breaks the build or tests. - Aspire and Plugin Awareness: Cross-checks Aspire.Hosting.* integration packages when an .AppHost project exists, and reports installed plugins that are behind their marketplace versions. - Use Case: Schedule a weekly run that scans your solution, updates safe packages, verifies dotnet build and dotnet test pass, waits for your approval, then opens a labeled pull request with the full audit table. ## Quick Start Run the schedule-package-update skill to audit and update all outdated NuGet packages in this solution and open a pull request with the results.

Frequently Asked Questions about schedule-package-update

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update all outdated NuGet packages in a .NET solution?▼

Run `dotnet list package --outdated` to audit packages, then update versions in Directory.Packages.props or individual .csproj files and run dotnet restore. This Skill automates that full cycle, verifies the build and tests, and opens a pull request.

How to update NuGet packages with Central Package Management?▼

With Central Package Management, edit the PackageVersion entries in Directory.Packages.props rather than per-project PackageReference versions. The Skill detects which packages are centrally managed and updates them in the correct location.

Does it handle major version upgrades automatically?▼

No. The default strategy is minor-and-patch only. Major version bumps are opt-in and require explicit user confirmation before being applied, since they may introduce breaking changes.

What happens if a package update breaks the build or tests?▼

The failing package update is reverted and recorded as Skipped (test failure) in the summary table. The run continues with the remaining packages rather than force-updating or aborting entirely.

Can it update Aspire integration packages?▼

Yes, when the solution contains an .AppHost project, the Skill cross-checks Aspire.Hosting.* and Aspire.* client integration packages and applies required configuration or API changes. This phase is skipped automatically without an AppHost.

Does the skill open a pull request without approval?▼

No. The Skill presents the audit table and build/test results and waits for explicit approval before pushing the branch and opening the PR. If approval is withheld, it stops and records the outcome.