skills.rest
lewing
lewingCOMMUNITY
Explore all skills by this author →
𝕏@lewingGitHub

dotnet-inspect

Inspect .NET library APIs across NuGet packages, platform libraries, and local DLLs.

Updated Feb 18, 2026
Search Tags:#dependencies#dotnet#nuget#extension-methods#api-analysis#dotnet-inspect#library-inspection
One-click install
npx skills add https://github.com/lewing/maestro.mcp --skill dotnet-inspect-lewing
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dotnet-inspect
Source: https://github.com/lewing/maestro.mcp/tree/main/.ai-team-backup/skills/dotnet-inspect
Command: npx skills add https://github.com/lewing/maestro.mcp --skill dotnet-inspect-lewing

SYSTEM DOCUMENTATION & REQUIREMENTS

## What problem does it solve? Query across NuGet packages, platform libraries, and local DLLs to understand .NET API surfaces and available types.

## Core Features & Use Cases

  • Discover types and members across NuGet packages, platform libraries, and local assemblies.
  • Compare API surfaces between versions to identify breaking or additive changes.
  • Find extension methods, implementors, and dependencies to navigate codebases.
  • Inspect packages and libraries to understand metadata and references.

### Quick Start Install dotnet-inspect and start by querying a package to list available types.

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 library APIs across NuGet packages and local DLLs?▼

You can discover available types and members across NuGet packages, platform libraries, and local DLLs by issuing commands like type, member, and library. The tool returns structured metadata detailing the API surface of your .NET libraries.

What is the best way to compare API surfaces between different package versions?▼

Comparing API surfaces between versions is done using the diff command, which identifies breaking or additive changes in .NET libraries. This allows you to track exactly what types or members were modified across different releases.

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

You can find extension methods and implementors in a .NET codebase by using the extensions command. This maps the relationships and dependencies within your libraries to help navigate real codebases effectively.

Do I need a specific NuGet package to inspect .NET types and dependencies?▼

Yes, you need the PCS client NuGet package and the dotnet-inspect tool to inspect .NET types and dependencies. These prerequisites enable querying local DLLs and platform libraries to return structured metadata.

Can I list package dependencies and references for local .NET assemblies?▼

Yes, you can list package dependencies and references for local .NET assemblies using the depends and package commands. This inspects the libraries to understand their metadata and external references.

Related Skills

Explore More Software Engineering Skills→
CommunityToolkitCommunityToolkit
619

dotnet-inspect

Analyze .NET APIs from NuGet packages, platform libraries, and local files.

Official
Advanced
sunholo-datasunholo-data
33

AILANG Release Manager

Automates end-to-end AILANG release management including pre-release checks, version bumps, changelog updates, git tagging, CI/CD verification, and release broadcasting.

Official
Intermediate
umbrella-librariesumbrella-libraries
8

nuget-safe-upgrade

Upgrade NuGet packages across multi-targeted .NET projects with exclusions and build verification.

Official
Advanced
cslsoftwarescslsoftwares

developer-delphi-language-rtti

Inspect and manipulate Delphi type information at runtime using RTTI.

Community
Advanced