dotnet-inspect

Enumerate .NET library types and API surfaces across NuGet packages and assemblies.

Updated Nov 11, 2025
One-click install
npx skills add https://github.com/eruvalca/Calcio --skill dotnet-inspect-eruvalca
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet-inspect
Source: https://github.com/eruvalca/Calcio/tree/main/.agents/skills/dotnet-inspect
Command: npx skills add https://github.com/eruvalca/Calcio --skill dotnet-inspect-eruvalca

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers often need to discover and compare APIs across NuGet packages, framework assemblies, and local binaries to understand available types, members, and changes.

Core Features & Use Cases

  • Type discovery: enumerate types in a package or assembly.
  • API surface inspection: view member signatures and documentation for types.
  • Diff across versions: compare changes between package versions to assess compatibility.
  • Extensions and implementors: locate extension methods and types that implement interfaces.

Quick Start

Ask the tool to list all types in a given package and show their available members for quick evaluation.

Frequently Asked Questions about dotnet-inspect

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

FAQPage Schema
How do I inspect and enumerate .NET types across NuGet packages and local assemblies?

To inspect .NET types across NuGet packages and local assemblies, you can enumerate all available types and view their member signatures using API surface inspection. This allows quick evaluation of library structures without manually browsing source code.

What is the best way to compare API changes between different .NET package versions?

Comparing API changes between .NET package versions is done through version diffing, which highlights member signature additions or removals to assess compatibility. This structured comparison reveals breaking changes across project versions.

How do I find extension methods and types implementing interfaces in a .NET assembly?

Finding extension methods and interface implementors in a .NET assembly requires type discovery and reflection. The tool scans local binaries and framework libraries to locate matching types and their members through structured outputs.

Can I use dotnet-inspect to check compatibility across framework libraries without external dependencies?

Yes, dotnet-inspect operates without external dependencies to inspect framework libraries. It analyzes local binaries and NuGet packages directly to evaluate API surfaces, type members, and version compatibility across your projects.

What limitations exist when inspecting local .NET binaries for API discovery?

When inspecting local .NET binaries for API discovery, limitations include relying on available reflection metadata within the assemblies. It focuses on type and member enumeration without executing code or analyzing runtime behavior.