# dotnet-inspect-compatibility

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.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 412 installs · ★ 167 repo stars
- Author: richlander
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/richlander/dotnet-inspect/tree/HEAD/skills/compatibility/SKILL.md
- Updated: 2026-11-04
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/dotnet-inspect-compatibility

## What it does

The `diff` command takes a version range like `Foo@1.0.0..2.0.0` 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.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add richlander/dotnet-inspect --skill dotnet-inspect-compatibility -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/compatibility/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/compatibility/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add richlander/dotnet-inspect --skill dotnet-inspect-compatibility -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/compatibility/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add richlander/dotnet-inspect --skill dotnet-inspect-compatibility -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/compatibility/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install richlander/dotnet-inspect skills/compatibility
```

2. **Manually: put the files in place**
- File: `.github/skills/compatibility/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add richlander/dotnet-inspect --skill dotnet-inspect-compatibility -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/richlander/dotnet-inspect --path skills/compatibility
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/compatibility/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add richlander/dotnet-inspect --skill dotnet-inspect-compatibility -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/richlander/dotnet-inspect/tree/HEAD/skills/compatibility/SKILL.md

## When to use it
- 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
- Run a breaking-change diff on `System.Text.Json` from 9.0.0 to 10.0.0
- Execute `dnx dotnet-inspect -y -- diff --package Foo@1.0.0..2.0.0 -S Changes` and explain any unclassified entries
- Trace the `Deserialize` overload on `JsonSerializer` from 9.0.0 to 10.0.0 using `member --match`

## Similar
- [api-design](https://affpapa.org/en/nevibecode/skills/aaronontheweb-api-design.md) — skill · 702 installs
- [dotnet-breaking-changes](https://affpapa.org/en/nevibecode/skills/dotnet-breaking-changes.md) — skill · 614 installs
- [dotnet-project-structure](https://affpapa.org/en/nevibecode/skills/dotnet-project-structure.md) — skill · 706 installs
- [dotnet-security](https://affpapa.org/en/nevibecode/skills/dotnet-security.md) — skill · 358 installs
- [dotnet-framework](https://affpapa.org/en/nevibecode/rules/dotnet-framework.md) — rule · ★ 41430 repo stars
- [dotnet](https://affpapa.org/en/nevibecode/skills/dotnet.md) — skill · 765 installs

From the same set: [richlander/dotnet-inspect](https://affpapa.org/en/nevibecode/by/richlander/dotnet-inspect.md) — 5 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
