skills.rest
AGIBuild
AGIBuildCOMMUNITY
Explore all skills by this author →
GitHub

dotnet-library-api-compat

Analyze .NET library API changes for binary and source compatibility.

10|Updated Jan 28, 2026
Search Tags:#api#compatibility#library#breaking changes#dotnet#semver
One-click install
npx skills add https://github.com/AGIBuild/Agibuild.Fulora --skill dotnet-library-api-compat
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dotnet-library-api-compat
Source: https://github.com/AGIBuild/Agibuild.Fulora/tree/main/.cursor/skills/dotnet-library-api-compat
Command: npx skills add https://github.com/AGIBuild/Agibuild.Fulora --skill dotnet-library-api-compat

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps .NET library authors understand and maintain binary and source compatibility with their consumers, preventing runtime and compile-time errors.

Core Features & Use Cases

  • Binary Compatibility Rules: Identifies API changes that break existing compiled code.
  • Source Compatibility Rules: Identifies API changes that break consumer source code compilation.
  • Type Forwarders: Explains how to move types between assemblies without breaking consumers.
  • SemVer Impact: Maps API changes to Semantic Versioning increments.
  • Use Case: You are releasing a new version of your popular .NET library. This Skill helps you determine if adding a new method overload will break existing users' code or if removing an old method requires a major version bump.

Quick Start

Use the dotnet-library-api-compat skill to analyze potential breaking changes for a new library release.

Frequently Asked Questions about dotnet-library-api-compat

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What .NET library changes break binary compatibility for existing compiled code?▼

Source compatibility is broken by API changes that cause consumer source code to fail compilation, such as modifying public type signatures. This Skill helps identify modifications that break source-level compilation for .NET library consumers.

How do I move types between .NET assemblies without breaking consumers?▼

Removing an old method from a .NET library requires a major version bump according to Semantic Versioning. This Skill maps specific API changes to their required SemVer increments to ensure correct library versioning.

Does this .NET API compatibility guidance apply to .NET 8.0 and modern SDK-style projects?▼

Yes, this API compatibility guidance focuses on the .NET 8.0+ baseline and modern SDK-style projects. It provides targeted rules for maintaining library compatibility within modern .NET development environments.

When do I need to check source compatibility versus binary compatibility for my .NET library?▼

You need to check source compatibility when changes affect consumer compilation, and binary compatibility when changes affect runtime execution of compiled code. This Skill distinguishes between safe and breaking API changes for both compatibility levels.

Related Skills

Explore More Software Engineering Skills→
rudironsonirudironsoni

dotnet-csharp-api-design

Guide public .NET API design with naming, parameter, and error conventions.

Community
Intermediate
rudironsonirudironsoni

dotnet-library-api-compat

Guide .NET library API changes for binary and source compatibility.

Community
Intermediate
icartshicartsh
4

code-analyze

Analyze .NET solutions for code quality, security, and dependency issues.

Community
Advanced
dodygdodyg

dotnet-library-api-compat

Detect binary and source compatibility risks for .NET library API changes.

Community
Intermediate