What problem does it solve? When a .NET application crashes in production, developers often lack the memory state needed to diagnose the failure. This Skill guides you through enabling automatic crash dump collection or capturing dumps on demand from running .NET processes, across Linux, macOS, Windows, Docker, and Kubernetes. ## Core Features & Use Cases - Automatic crash dump configuration: Set up DOTNET_DbgEnableMiniDump environment variables for CoreCLR apps, or OS-level core dumps (ulimit, core_pattern, WER) for NativeAOT apps. - On-demand capture: Collect dumps from running processes using dotnet-dump collect, gcore, lldb, or procdump depending on platform and runtime. - Container support: Configure Docker and Kubernetes workloads with SYS_PTRACE capability, volume mounts, and pod specs so dumps persist outside the container. - Use Case: Your NativeAOT service keeps crashing in a Kubernetes pod. Use this Skill to add the right security context, environment variables, and a persistent volume so a full dump is written to /dumps on the next crash. ## Quick Start Ask the assistant to enable automatic crash dump collection for your .NET application, specifying the platform, runtime (CoreCLR or NativeAOT), and whether it runs in a container.
