csharp-decompile

majiayu000's avatarfrom majiayu000

Decompile .NET assemblies to inspect types, understand implementations, debug third-party libraries, and view IL code. Use when debugging NuGet dependency behavior, understanding compiled code, investigating runtime issues, or exploring unfamiliar assemblies.

⭐5stars🔀1forks📁View on GitHub🕐Updated Jan 11, 2026
[Debugging]

When & Why to Use This Skill

This Claude skill enables seamless decompilation of .NET assemblies using ilspycmd. It allows developers to inspect types, understand complex implementations, and debug third-party NuGet libraries by converting compiled code back into readable C# or Intermediate Language (IL). It is an essential tool for troubleshooting runtime issues, exploring unfamiliar assemblies, and recovering source code when original files are unavailable.

Use Cases

  • Debugging NuGet Dependencies: Inspect the internal logic of third-party libraries to identify bugs or unexpected behaviors when source code is not provided.
  • Legacy Code Exploration: Decompile older .NET assemblies to understand their structure and logic, facilitating maintenance or migration of legacy systems.
  • Low-Level Analysis: View and analyze Intermediate Language (IL) code to investigate performance bottlenecks or compiler-generated code patterns.
  • Project Reconstruction: Generate a complete, compilable C# project from a DLL to enable deep code exploration and modification using standard IDE tools.
  • Type Relationship Visualization: Generate interactive HTML diagrams to understand complex class hierarchies and dependencies within an assembly.
namecsharp-decompile
descriptionDecompile .NET assemblies to inspect types, understand implementations, debug third-party libraries, and view IL code. Use when debugging NuGet dependency behavior, understanding compiled code, investigating runtime issues, or exploring unfamiliar assemblies.

C# Decompilation with ilspycmd

Decompile .NET assemblies to C# source code or IL using ilspycmd.

Setup

Ensure ilspycmd is installed:

ilspycmd --version || dotnet tool install --global ilspycmd

Workflows

List Types in an Assembly

Discover what's in an assembly before decompiling:

# List all types: classes, interfaces, structs, delegates, enums
ilspycmd -l cisde /path/to/assembly.dll

Decompile to a Project

Generate a compilable C# project from an assembly:

ilspycmd --nested-directories -p -o /tmp/decompiled /path/to/assembly.dll

This creates a .csproj and source files organized by namespace.

Important: this lets Claude code bring its sophisticated code reading and exploration tools to bear.

Decompile a Specific Type

Target a single type by its fully qualified name:

ilspycmd -t MyNamespace.MyClass /path/to/assembly.dll

The output goes to stdout. Use this to quickly inspect a type's implementation.

View IL Code

For low-level analysis, view the intermediate language:

ilspycmd -il -t MyNamespace.MyClass /path/to/assembly.dll

# With sequence points (source line mappings)
ilspycmd --il-sequence-points -t MyNamespace.MyClass /path/to/assembly.dll

Debug NuGet Dependencies

NuGet packages are at ~/.nuget/packages/<package-name>/<version>/lib/<tfm>/. To inspect:

# Find the DLL
find ~/.nuget/packages/sixlabors.imagesharp -name "*.dll" | grep -v ref

# List types
ilspycmd -l cisde ~/.nuget/packages/sixlabors.imagesharp/3.1.11/lib/net6.0/SixLabors.ImageSharp.dll

# Decompile a specific type
ilspycmd -t "SixLabors.ImageSharp.Numerics" ~/.nuget/packages/sixlabors.imagesharp/3.1.11/lib/net6.0/SixLabors.ImageSharp.dll

Generate Type Diagrams

Create an interactive HTML visualization of type relationships:

ilspycmd --generate-diagrammer -o /tmp/diagrammer /path/to/assembly.dll

# With filtering
ilspycmd --generate-diagrammer -o /tmp/diagrammer \
  --generate-diagrammer-include "MyNamespace\\..*" \
  --generate-diagrammer-exclude "MyNamespace\\.Internal\\..*" \
  /path/to/assembly.dll

These are mostly useful for the user. Let the user know that they're available.

Tips

  • Add -r /path/to/deps when the assembly has dependencies that aren't automatically resolved
  • Use --no-dead-code and --no-dead-stores for cleaner output
  • For tight loops or scripts, add --disable-updatecheck
  • The -lv Latest flag is default; use -lv CSharp9_0 etc for older language features

Fixes