agentleFS
andy-dendy-repoandy-dendy-repo/govern/.claude/skills/outdated-packages/SKILL.md

outdated-packages

Skill2 starsChanged 32 days agoMITView on GitHub

Checks Govern's NuGet packages for vulnerable, deprecated and outdated versions and upgrades them safely through central package management, then verifies. Use when the user asks to update/upgrade packages, when CI reports vulnerable packages, or periodically before a release.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    All versions live in Directory.Packages.props (central package management with transitive pinning).

    line 12
  2. Distinctive:

    Ask the user before any major upgrade.

    line 34
  3. Very specific:

    Run /verify: build (warnings are errors), format, and all tests including the Testcontainers integration tests.

    line 42

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Outdated packages

All versions live in Directory.Packages.props (central package management with transitive pinning). Never pick versions from memory; query NuGet.

1. Report

dotnet list Govern.slnx package --vulnerable --include-transitive
dotnet list Govern.slnx package --deprecated
dotnet list Govern.slnx package --outdated

Summarise the results as a table: package, current version, latest version, kind (security / major / minor / patch), projects.

2. Plan

Handle the categories in this order:

  1. Vulnerable packages (security): upgrade first.
  2. Deprecated packages: follow the suggested replacement.
  3. Patch and minor versions: batch together.
  4. Major versions: one package family per change. Read the release notes (context7 / microsoft-docs) and list the breaking changes before upgrading.

Keep families aligned:

  • Microsoft.AspNetCore.*, Microsoft.Extensions.* and Microsoft.EntityFrameworkCore.* move together.
  • Npgsql.EntityFrameworkCore.PostgreSQL follows the EF Core major version.
  • Microsoft.CodeAnalysis.CSharp is pinned to the Roslyn version required by Microsoft.EntityFrameworkCore.Design. Check its dependency before moving it.

Ask the user before any major upgrade.

3. Upgrade

  • Edit the Version attributes in Directory.Packages.props, or use dotnet add <project> package <Name> without --version to get the latest.
  • A restore hook runs automatically. NU1107/NU1608 conflicts mean a transitive pin disagrees: align the family or add an explicit pin with a comment explaining why.
  • dotnet-ef in dotnet-tools.json should match the EF Core version.

4. Verify

Run /verify: build (warnings are errors), format, and all tests including the Testcontainers integration tests. Also check:

  • az bicep build --file infra/main.bicep, when infra tooling changed
  • docker build via dotnet publish src/Govern.Api -t:PublishContainer, when the runtime or SDK changed. Keep global.json and the container base image on the same major version.

5. Report

  • The before and after table.
  • Anything skipped, and why (e.g. a major upgrade waiting for approval).
  • The test summary from the real run.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.