Skip to main content
skill CX Codex

dotnet-inspect-compatibility — Claude Code skill for .NET API diffing

dotnet-inspect-compatibility — a skill for Claude Code, Codex, Cursor and other agents that compares .NET library versions across public API, implementation and static analysis.

no license 412 installs ★ 167 updated 2026-11-04

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add richlander/dotnet-inspect --skill dotnet-inspect-compatibility -a claude-code
Open on GitHub

What dotnet-inspect-compatibility does

The diff command takes a version range like [email protected] and returns API changes: --breaking filters assessed breaks, --additive selects additions, -S Changes pulls the full set including unclassified entries. Unclassified does not mean safe.

Beyond API shape, Analysis Diff surfaces shifts in allocation, unsafe code and exception throwing between versions. The --implementation flag compares reconstructed C# and IL; identical IL does not establish behavioral equivalence, and decompiled C# is not the original source. To follow one member through version history, member --match tracks declaration correspondence from the source coordinate — the same overload position at the destination is a separate lookup, not an identity match.

Locating when a change appeared uses diff --history with --at first or --at last; the approach is to walk backward from the broken version because binary search requires a monotonic predicate. An incomplete or rejected comparison is not "no changes" — the CLI exit status and diagnostics carry that verdict.

What it helps with

  • diff two NuGet package versions for breaking public API changes
  • trace a specific method's declaration through a package version range
  • find the version where a hot-path allocation first appeared
  • compare IL between two assemblies to spot implementation divergence
  • identify the boundary version where an overload was added or removed

Example prompts for the agent

  • Run a breaking-change diff on System.Text.Json from 9.0.0 to 10.0.0
  • Execute dnx dotnet-inspect -y -- diff --package [email protected] -S Changes and explain any unclassified entries
  • Trace the Deserialize overload on JsonSerializer from 9.0.0 to 10.0.0 using member --match

How to install dotnet-inspect-compatibility

1Skills CLI (Vercel)

npx skills add richlander/dotnet-inspect --skill dotnet-inspect-compatibility -a claude-code

2Manually: put the files in place

~/.claude/skills/compatibility/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/compatibility/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about dotnet-inspect-compatibility

How do I install dotnet-inspect-compatibility in Claude Code?

Run npx skills add richlander/dotnet-inspect --skill dotnet-inspect-compatibility -a claude-code. The skill is then available at ~/.claude/skills/compatibility/SKILL.md.

What does dotnet-inspect-compatibility do?

It gives the agent a structured way to compare .NET library versions: finding breaking and additive API changes, examining IL and reconstructed C# for implementation shifts, and tracking a specific type member across a package history.

Does an empty breaking-changes result mean the upgrade is safe?

No. An incomplete or rejected comparison is not the same as no changes — read the exit status and CLI diagnostics. Entries in -S Changes marked unclassified carry no safety verdict in either direction.

Similar skills

All skills for Programming languages →

From the same set5

Project sponsors

Companies that keep this analytics open