nuget-decompile-with-ilspycmd

What problem does it solve?

When a C# type, enum, method, or namespace appears only as a usage in a repository and its definition is not present in source, this Skill provides a repeatable process to find the candidate NuGet package and DLL and to verify the actual API surface by decompiling with ilspycmd so answers do not rely on guesswork.

Core Features & Use Cases

• Prioritize detection of company namespaces (for example HousePrice.* and Evertrust.*) and map them to likely package/DLL candidates rather than assuming the package name equals the namespace.
• Inspect project files (csproj, Directory.Packages.props, packages.lock.json, obj/project.assets.json), search the local NuGet cache for candidate DLLs, and validate types using ilspycmd; prefer adjacent XML files for summaries.
• Produce a verifiable report listing whether the symbol is external, which package and version the project consumes, the DLL path inspected, and the fully-qualified decompiled type signature or enum members (with values inferred when not explicit).
• Use cases: resolving missing enum members, confirming method signatures, recovering XML summaries, and prioritizing candidate DLLs for company-specific namespaces.

Quick Start

Search the repository for the missing symbol and package references, locate the matching DLL in your local NuGet cache, and use ilspycmd to inspect the fully-qualified type and any sibling XML summaries.