How do I install the Shine Update Nugets skill?

Run npx skillmds@latest add pavelt-papaya/shine-update-nugets in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Shine Update Nugets safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Shine Update Nugets?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Shine Update Nugets free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Shine Update Nugets?

pavelt-papaya (@pavelt-papaya) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Shine Update Nugets by pavelt-papaya

Name: Shine Update Nugets
Author: pavelt-papaya

Shine Update Nugets

Restores .NET packages, reports outdated NuGet versions from the solution, and proposes safe version bumps for non–Hot-Chocolate dependencies. Does not change Hot Chocolate / ChilliCream-related package versions at all (no patch, minor, or major bumps). Use when the user asks to update NuGets, check package updates, bump dependencies, refresh NuGet versions, or Shine-related .NET dependency updates.

pavelt-papaya Updated Sep 22, 2026

File contents

Shine: Update NuGets (.NET)

Goals

Restore packages so the graph is current and buildable.
List outdated packages and what newer versions exist.
Update non–ChilliCream packages toward current stable releases as the user requests.
Do not change ChilliCream / Hot Chocolate ecosystem package versions at all—not patch, not minor, not major (even if newer 13.x exists). Report them as informational only if useful.

ChilliCream ecosystem (do not modify versions)

Treat any package whose id matches these patterns as Hot Chocolate–related—never bump, suggest, or edit their versions:

HotChocolate.*
StrawberryShake.* (includes “Strawberry” client/tooling packages)
GreenDonut*
CookieCrumble*
ChilliCream.* (if present)

If unsure whether a package is ChilliCream, check the package page on nuget.org (publisher / dependencies).

Rule: Leave these packages exactly as pinned in the repo. You may mention in the report that newer versions exist on NuGet, but state clearly that they were not updated by design.

Workflow

1. Restore

From the repository root (or solution directory):

dotnet restore

Fix any restore errors before continuing.

2. Outdated packages

Prefer solution-wide listing when a .sln exists:

dotnet list <path-to.sln> package --outdated

Optional (more noise, fuller picture):

dotnet list <path-to.sln> package --outdated --include-transitive

If there is no solution file, run the same command per .csproj or discover projects with find/glob.

3. Interpret results

Split the table into:
- ChilliCream / Hot Chocolate: ids matching the patterns above → no version changes. Optionally list “newer on NuGet” for awareness only.
- Other: safe to plan upgrades per user instruction (respect any other repo pins, e.g. InfraVersion, internal Shine.* packages).

4. Apply version changes

If the repo uses Central Package Management (Directory.Packages.props, ManagePackageVersionsCentrally), edit PackageVersion entries there—not scattered PackageReference versions unless the project does not use CPM.
Do not edit PackageVersion lines or MSBuild properties (e.g. HotChocolateVersion) for any ChilliCream / Hot Chocolate–related package.
After edits: dotnet restore again, then dotnet build (or test) to verify.

5. Report to the user

Summarize:

What was restored / built.
Outdated list grouped into ChilliCream / Hot Chocolate (unchanged) vs other (what was updated or proposed).
Exact file edits (paths + version changes) or a short table.

Do not

Change any Hot Chocolate / ChilliCream-related package version (including HotChocolateVersion and every matching PackageVersion).
Assume “Strawberry*” packages are safe to bump—they are the same vendor; leave them untouched like HotChocolate.*.
Commit or push unless the user explicitly asks (follow repo / user rules).

---name: shine-update-nugetsdescription: Restores .NET packages, reports outdated NuGet versions from the solution, and proposes safe version bumps for non–Hot-Chocolate dependencies. Does not change Hot Chocolate / ChilliCream-related package versions at all (no patch, minor, or major bumps). Use when the user asks to update NuGets, check package updates, bump dependencies, refresh NuGet versions, or Shine-related .NET dependency updates.---# Shine: Update NuGets (.NET)## Goals1. Restore packages so the graph is current and buildable.2. List outdated packages and what newer versions exist.3. Update **non–ChilliCream** packages toward current stable releases as the user requests.4. **Do not** change ChilliCream / Hot Chocolate ecosystem package versions **at all**—not patch, not minor, not major (even if newer 13.x exists). Report them as informational only if useful.## ChilliCream ecosystem (do not modify versions)Treat any package whose **id** matches these patterns as Hot Chocolate–related—**never bump, suggest, or edit** their versions:- `HotChocolate.*`- `StrawberryShake.*` (includes “Strawberry” client/tooling packages)- `GreenDonut*`- `CookieCrumble*`- `ChilliCream.*` (if present)If unsure whether a package is ChilliCream, check the package page on nuget.org (publisher / dependencies).**Rule:** Leave these packages exactly as pinned in the repo. You may mention in the report that newer versions exist on NuGet, but state clearly that they were **not** updated by design.## Workflow### 1. RestoreFrom the repository root (or solution directory):```bashdotnet restore```Fix any restore errors before continuing.### 2. Outdated packagesPrefer solution-wide listing when a `.sln` exists:```bashdotnet list <path-to.sln> package --outdated```Optional (more noise, fuller picture):```bashdotnet list <path-to.sln> package --outdated --include-transitive```If there is no solution file, run the same command per `.csproj` or discover projects with `find`/`glob`.### 3. Interpret results- Split the table into: - **ChilliCream / Hot Chocolate**: ids matching the patterns above → **no version changes**. Optionally list “newer on NuGet” for awareness only. - **Other**: safe to plan upgrades per user instruction (respect any other repo pins, e.g. `InfraVersion`, internal `Shine.*` packages).### 4. Apply version changes- If the repo uses **Central Package Management** (`Directory.Packages.props`, `ManagePackageVersionsCentrally`), edit **`PackageVersion`** entries there—not scattered `PackageReference` versions unless the project does not use CPM.- **Do not** edit `PackageVersion` lines or MSBuild properties (e.g. `HotChocolateVersion`) for any ChilliCream / Hot Chocolate–related package.- After edits: `dotnet restore` again, then `dotnet build` (or test) to verify.### 5. Report to the userSummarize:- What was restored / built.- Outdated list grouped into **ChilliCream / Hot Chocolate (unchanged)** vs **other** (what was updated or proposed).- Exact file edits (paths + version changes) or a short table.## Do not- Change **any** Hot Chocolate / ChilliCream-related package version (including `HotChocolateVersion` and every matching `PackageVersion`).- Assume “Strawberry*” packages are safe to bump—they are the same vendor; **leave them untouched** like `HotChocolate.*`.- Commit or push unless the user explicitly asks (follow repo / user rules).

Frequently asked questions