dump-collect

Topics in the source

• .NET Crash Dump Collection
• Stop Signals
• Step 1 — Identify the Scenario
• Detecting CoreCLR vs NativeAOT
• Step 2 — Load the Appropriate Reference
• Step 3 — Execute

Cratis rules in .cratis/ai/rules/ (including csharp.md, specs.csharp.md, and orleans.md) and the cratis- skills win where they differ. Dumps contain all process memory, including secrets and personal data: keep them local and task-scoped, never attach to issues or PRs; changing the host corepattern needs the user's approval. This skill configures and collects crash dumps for modern .NET applications (CoreCLR and NativeAOT) on Linux, macOS, and Windows — including containers. 🚨 Read before starting any workflow. Stop after dumps are enabled or collected. Do not open, analyze, or triage dump files. If the user already has a dump file, this skill does not cover analysis. Let them know analysis is out of scope. Do not install analysis tools (dotnet-dump analyze, windbg). Only install collection tools (dotnet-dump collect). Using lldb for on-demand dump capture on macOS is allowed — it ships with Xcode command-line tools and is not being used for analysis. Do not trace root cause of crashes. Report the dump file location and move on. Do not modify application code. Configuration is environment-only (env vars, OS settings, container specs). Ask or determine: 1. Goal: Enable automatic cr

This is an excerpt. Refer to the complete source and its current requirements.