dotnet-inspect

Discover and inspect .NET API types, members, and signatures across NuGet packages and local DLLs.

46|6|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/elbruno/ElBruno.MarkItDotNet --skill dotnet-inspect-elbruno
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet-inspect
Source: https://github.com/elbruno/ElBruno.MarkItDotNet/tree/main/.agents/skills/dotnet-inspect
Command: npx skills add https://github.com/elbruno/ElBruno.MarkItDotNet --skill dotnet-inspect-elbruno

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Querying and understanding .NET APIs across NuGet packages, platform libraries, and local assemblies is time-consuming and error-prone; this Skill centralizes discovery, inspection, and comparison to accelerate AI-assisted coding and API research.

Core Features & Use Cases

  • Discover types across NuGet and frameworks, list API surfaces, and inspect member signatures with inline docs.
  • Compare API surfaces between package versions and find extensions or implementors for interfaces.
  • Explore dependencies and metadata to plan migrations or integrate with AI pipelines for documentation.

Quick Start

Ask dotnet-inspect to list the API surface of a package like System.Text.Json and compare it with a previous version.

Frequently Asked Questions about dotnet-inspect

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

FAQPage Schema
How do I inspect .NET API surfaces across NuGet packages?

You can inspect .NET API surfaces by querying NuGet package metadata to discover types, list members, and view signatures with inline documentation. This Skill centralizes discovery and inspection for codebases and documentation tasks.

Can I compare API differences between NuGet package versions?

Yes, you can compare API surfaces between NuGet package versions by applying API diffing. This highlights changes in types and members, helping you plan migrations or track breaking changes across releases.

How do I find extension methods and implementors in a .NET codebase?

You can find extension methods and implementors by exploring types and members across local assemblies and NuGet packages. The Skill locates extensions and interface implementations to assist with API research and integration tasks.

Does this work with local DLLs or only NuGet sources?

It works with both local DLLs and NuGet sources. You can explore .NET APIs across local assemblies, platform libraries, and NuGet packages to discover types, inspect members, and compare API surfaces regardless of the source.

What is the best way to discover types in .NET platform libraries?

The best way to discover types in .NET platform libraries is to query the library metadata and perform type discovery across frameworks. You can list API surfaces and inspect member signatures to understand available functionality.

Are there limitations when diffing API surfaces across .NET versions?

API diffing across .NET versions relies on available package metadata and local assembly access. It compares type and member signatures effectively, but complex runtime behaviors or dynamic implementations may not be fully captured.