From dotnet-skills
Inspects .NET packages, assemblies, APIs, dependencies, and API diffs. Reports evidence for types, members, SourceLink, and breaking changes.
How this skill is triggered — by the user, by Claude, or both
Slash command
/dotnet-skills:dotnet-inspectThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use dotnet-inspect when you need evidence instead of guesses for .NET packages, platform libraries, local assemblies, APIs, dependencies, SourceLink/source, or version-to-version API changes.
Use dotnet-inspect when you need evidence instead of guesses for .NET packages, platform libraries, local assemblies, APIs, dependencies, SourceLink/source, or version-to-version API changes.
Invoke with dnx:
dnx dotnet-inspect -y -- <command>
This marketplace skill is intentionally only a bootstrapper. For non-trivial work, first run the version-matched embedded guide:
dnx dotnet-inspect -y -- skill
Prefer that embedded guide when commands, output modes, section names, or workflow guidance differ.
| Goal | Command |
|---|---|
| Find where an API lives | find Pattern |
| Inspect types or members | type Type --package Foo, then member Type --package Foo |
| Compare versions | diff --package [email protected] --breaking |
| Inspect package/library signals | package Foo -S Signals or library Foo -S Signals |
| Locate source or implementation | source Type --package Foo or member Type Member:1 -S "Decompiled Source" |
| Explore relationships | depends Type, extensions Type, implements Interface |
After find, reuse the package, library, or platform scope it reports. Quote generic type names such as 'List<T>'; use <T>, not <>.
npx claudepluginhub richlander/dotnet-skills --plugin dotnet-skillsInspects .NET packages, platform libraries, local assemblies, APIs, dependencies, SourceLink/symbol provenance, and version-to-version API changes with structured evidence (markdown, table, JSON, mermaid).
Decompiles .NET assemblies with ILSpy via dnx to inspect internal API implementations, NuGet packages, framework code, and binaries. Use for understanding compiled .NET behavior.
Decompiles .NET assemblies using ILSpy to reveal API implementations, NuGet package source, framework code, and binary internals. Use for inspecting compiled .NET binaries.