v0.6.0

What's Changed

This release introduces dotnet-change-impact, a new skill for classifying .NET library and NuGet package changes against Microsoft's official compatibility rules. The skill automatically determines whether a change warrants a Major, Minor, or Patch version bump, helping teams avoid accidental breaking releases while staying practical about what truly requires a major bump. When no explicit change details are provided, the skill inspects the current Git branch and compares it against the upstream default branch.

Key capabilities:

• Semantic versioning guidance grounded in Microsoft's official .NET library compatibility model (https://learn.microsoft.com/en-us/dotnet/core/compatibility/),
• Multi-faceted change analysis covering breaking changes, API diffs, public API changes, dependency updates, TFM and platform support changes, interface and enum modifications, overloads, analyzers, and source generators,
• Automatic default-branch resolution when no explicit change details are provided; the skill detects the current Git branch and compares against the upstream remote default branch with intelligent fallback to main or master,
• Comprehensive compatibility-categories reference documenting the five compatibility buckets (Binary, Source, Behavioral, Design-time, and Backwards compatibility) with worked examples and special-case catalog,
• Structured recommendation output with Key changes identified, Compatibility impact analysis, Reasoning, and Deterministic decision sections,
• Per-skill eval coverage validating current-branch detection, breaking-change scenarios, API compatibility assessments, dependency updates, and SemVer classification.

Sources:

• V0.6.0/dotnet change impact by @gimlichael in #21

Full Changelog: v0.5.0...v0.6.0