dotnet-library-api-compat

Installation
SKILL.md

dotnet-library-api-compat

Binary and source compatibility rules for .NET library authors. Covers which API changes break consumers at the binary level (assembly loading, JIT resolution) versus at the source level (compilation), how to use type forwarders for assembly reorganization without breaking consumers, and how versioning decisions map to SemVer major/minor/patch increments.

Version assumptions: .NET 8.0+ baseline. Compatibility rules apply to all .NET versions but examples target modern SDK-style projects.

Scope

  • Binary compatibility rules (safe vs breaking changes, runtime failures)
  • Source compatibility rules (overload resolution, extension method conflicts)
  • Type forwarders for assembly reorganization
  • SemVer impact mapping (change category to major/minor/patch)
  • Deprecation lifecycle with [Obsolete]
  • EnablePackageValidation and ApiCompat verification

Out of scope

  • HTTP API versioning -- see [skill:dotnet-api-versioning]
  • NuGet package metadata, signing, and publish workflows -- see [skill:dotnet-nuget-authoring]
Related skills

More from novotnyllc/dotnet-artisan

Installs
3
GitHub Stars
208
First Seen
Feb 24, 2026