skills.rest
ecoDriverltd
ecoDriverltdOFFICIAL
Explore all skills by this author →
WebsiteGitHub

dotnet-inspect

Inspect .NET packages, assemblies, APIs, dependencies, and version diffs for evidence.

Updated Jul 2, 2026
Search Tags:#dependencies#dotnet#nuget#api inspection#assembly analysis#sourcelink#package diff
One-click install
npx skills add https://github.com/ecoDriverltd/FoundryAgentsExperiment --skill dotnet-inspect-ecodriverltd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dotnet-inspect
Source: https://github.com/ecoDriverltd/FoundryAgentsExperiment/tree/main/.agents/skills/dotnet-inspect
Command: npx skills add https://github.com/ecoDriverltd/FoundryAgentsExperiment --skill dotnet-inspect-ecodriverltd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It replaces guesswork about .NET packages, platform libraries, assemblies, and APIs with verifiable evidence, so you can confirm where an API lives, what changed between versions, and how types relate before writing code. ## Core Features & Use Cases - API Discovery: Find where an API lives with find, then drill into types and members with type and member commands. - Version Comparison: Diff package versions with diff --package Foo@old..new --breaking to surface breaking changes before upgrading. - Source and Dependency Analysis: Locate SourceLink or decompiled source, and explore relationships with depends, extensions, and implements. - Use Case: Before upgrading a NuGet package, run a diff to list breaking API changes, then inspect the affected types and their source to plan the migration. ## Quick Start Ask the agent to use the dotnet-inspect skill to find which package contains a specific .NET API or to compare two versions of a package for breaking changes.

Frequently Asked Questions about dotnet-inspect

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

FAQPage Schema
How do I find which NuGet package contains a .NET API?▼

Run the find command with a pattern, such as dnx dotnet-inspect -y -- find Pattern. It reports the package, library, or platform scope where the API lives, which you can reuse in follow-up type or member commands.

How to compare two versions of a .NET package for breaking changes?▼

Use the diff command with a version range, for example dnx dotnet-inspect -y -- diff --package Foo@old..new --breaking. This lists API differences between the two versions, filtered to breaking changes.

Can I view the source code of a .NET type from a package?▼

Yes, use the source command, such as dnx dotnet-inspect -y -- source Type --package Foo, to locate SourceLink source. You can also request decompiled source for a specific member with the member command and the Decompiled Source section.

Why does dotnet-inspect need the -y and -- flags with dnx?▼

The -y flag prevents interactive prompts during tool execution, and the -- separator ensures subsequent arguments are passed to dotnet-inspect rather than dnx itself. Always include both when invoking the tool.

How do I inspect generic .NET types like List<T>?▼

Quote generic type names using angle brackets with the type parameter, such as 'List<T>'. Use the <T> syntax rather than empty angle brackets so the tool can resolve the type correctly.

Related Skills

Explore More Software Engineering Skills→
CommunityToolkitCommunityToolkit
619

dotnet-inspect

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

Official
Advanced
githubgithub
38.5k

dotnet-upgrade

Generates prompts for analyzing and executing .NET framework upgrade workflows.

Official
Intermediate
THRISHAL12345THRISHAL12345

github-copilot-upgrader

Upgrade the @github/copilot package and validate type and build regressions.

Community
Advanced
swyxioswyxio
154

youtube-studio-computer-use

Automate browser-driven YouTube Studio edits for thumbnails, schedules, and metadata.

Community
Advanced