skills.rest
h4v1d
h4v1dCOMMUNITY
Explore all skills by this author →
GitHub

csharp-dotnet-debugging

Diagnose .NET runtime issues in C# applications using CLI tools.

Updated Dec 9, 2025
Search Tags:#debugging#dotnet#deadlock#diagnose#cpu#memory-leak#crash
One-click install
npx skills add https://github.com/h4v1d/extension-collection-geminicli --skill csharp-dotnet-debugging
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: csharp-dotnet-debugging
Source: https://github.com/h4v1d/extension-collection-geminicli/tree/main/csharp-dotnet-debugging
Command: npx skills add https://github.com/h4v1d/extension-collection-geminicli --skill csharp-dotnet-debugging

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enables developers to diagnose and pinpoint root causes of .NET/C# runtime problems using CLI-based tools, reducing time to resolution.

Core Features & Use Cases

  • CLI-driven diagnosis for memory leaks, high CPU usage, crashes, deadlocks, and performance regressions in .NET 10 applications.
  • Tooling orchestration with dotnet-counters, dotnet-dump, dotnet-trace, and dotnet-stack to collect data and analyze behavior.
  • Guided workflows that produce actionable root-cause recommendations and safe, repeatable remediation steps for production and development environments.

Quick Start

  • Diagnose a running .NET process by providing its PID, e.g. diagnose the process with PID <PID> for memory leaks and CPU hotspots.
  • Or specify a crash scenario to generate a dump and analyze stack traces with dotnet-dump.

Frequently Asked Questions about csharp-dotnet-debugging

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I diagnose memory leaks and high CPU usage in a running .NET application?▼

To diagnose memory leaks and high CPU usage in a .NET application, provide the process PID to orchestrate CLI tools like dotnet-counters and dotnet-trace, collecting runtime data to derive actionable root-cause fixes.

What is the best way to analyze a .NET crash dump for deadlocks?▼

The best way to analyze a .NET crash dump for deadlocks is to generate a dump file and analyze stack traces using dotnet-dump and dotnet-stack, enabling guided workflows that pinpoint exact root causes.

Can I use dotnet-trace and dotnet-dump to troubleshoot performance regressions in .NET 10?▼

Yes, you can troubleshoot performance regressions in .NET 10 by orchestrating dotnet-trace and dotnet-dump to collect diagnostic data, producing safe and repeatable remediation steps for production environments.

Do I need a specific process ID to start diagnosing runtime issues with dotnet tools?▼

You need the specific process ID (PID) to diagnose runtime issues in a running application, or you can specify a crash scenario to automatically generate a dump for stack trace analysis.

How does CLI-driven debugging handle root-cause analysis for C# applications?▼

CLI-driven debugging handles root-cause analysis for C# applications by orchestrating dotnet-counters, dotnet-dump, dotnet-trace, and dotnet-stack to collect data and derive actionable fixes for runtime problems.

What limitations exist when using dotnet tools for production debugging?▼

While metadata confirms CLI-driven debugging provides safe and repeatable remediation steps for production environments, specific limitations regarding overhead or compatibility constraints are not detailed.

Related Skills

Explore More Software Engineering Skills→
rudironsonirudironsoni
1

dotnet-windbg-debugging

Analyze Windows crash dumps and live processes with WinDbg.

Community
Advanced
geoffjaygeoffjay
8

tokio-troubleshooting

Diagnose deadlocks, leaks, and performance issues in Tokio runtimes.

Community
Advanced
MCCTeamMCCTeam
2.1k

csharp-dotnet-cli-optimization

Diagnose .NET process performance and memory pressure using CLI diagnostics.

Official
Advanced
Snowflake-LabsSnowflake-Labs
12

read-ors-configuration

A concise summary of your roleplay character: name,</name> personality, and/or behavior, formatted as a single string sentence. Typically不超过50字，此处省略

Official
Intermediate