.NET Change Impact

Classify a proposed change to a .NET library or NuGet package and recommend the correct release bump. This skill exists to stop accidental breaking releases from being shipped as a patch or minor, while staying practical enough not to label every internal refactor as breaking.

It answers one question:

Given these changes, should I bump Major, Minor, or Patch?

The authority for every decision is Microsoft's official .NET compatibility guidance:

• https://learn.microsoft.com/en-us/dotnet/core/compatibility/library-change-rules
• https://learn.microsoft.com/en-us/dotnet/core/compatibility/categories

Treat those two sources as normative. When the deep category definitions or the long tail of special cases matter, read references/compatibility-categories.md.

Input