csharp-decompile
/csharp-decompile
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.
- Author
- j-r-beckett ↗
- Repository
- SpeedReader ↗
- Licence
- Apache-2.0
- Last repository change
- 22.05.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 22.05.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
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.
Original author description
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.
How it works
- Setup
- Workflows
- Tips
- Fixes
SKILL.md preview
--- name: csharp-decompile description: 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. --- # C# Decompilation with ilspycmd Decompile .NET assemblies to C# source code or IL using `ilspycmd`. ## Setup Ensure ilspycmd is installed: ```bash ilspycmd --version || dotnet tool install --global ilspycmd ``` ## Workflows ### List Types in an Assembly Discover what's in an assembly before decompiling: ```bash # 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: ```bash 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: ```bash 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: ```bash 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: ```bash # 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: ```bash 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
Versions
The database has no other skills named csharp-decompile.
Database snapshot: 13.11.2026 · package version cbf36f7e2a39 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100ilspy-decompile
Understand implementation details of .NET code by decompiling assemblies. Use when you want to see how a .NET API works internally, inspect NuGet package source, view framework implementation, or understand compiled .NET binaries. - 100ilspy-decompile
Understand implementation details of .NET code by decompiling assemblies. Use when you want to see how a .NET API works internally, inspect NuGet package source, view framework implementation, or understand compiled .NET binaries. - 100ilspycmd
Decompile .NET assemblies to C# source. Trigger on inspect DLL, recover source code, decompile EXE, extract API surface, or understand third-party library internals. - 90sherlock
Inspect compiled .NET assemblies with the Sherlock MCP tools. Use when a task needs facts about a .NET API - a type's members, a method's signature or overloads, which types implement an interface, who calls a method, what a NuGet package exposes - or before writing C# against a… - 100dotnet-inspect
Query .NET APIs across NuGet packages, platform libraries, and local files. Search for types, list API surfaces, compare and diff versions, find extension methods and implementors. Use whenever you need to answer questions about .NET library contents. - 100sui-decompile
Use when fetching or analyzing deployed SUI Move contract source code from on-chain bytecode. Triggers on "decompile", "show me the contract code", "reverse engineer", "read on-chain module", "analyze deployed package", or when the user provides a package ID and wants to…