dotnet-diag
Overview
Use this skill for .NET diagnostics, performance investigations, runtime debugging, memory analysis, tracing, and incident response workflows from dotnet/skills.
Workflow
- Capture the symptom, runtime version, hosting model, traffic pattern, and recent changes.
- Prefer concrete evidence: logs, traces, dumps, metrics, profiler output, and reproducible commands.
- Separate observation, hypothesis, experiment, and conclusion.
- Recommend the smallest corrective change and the validation signal that proves it.
Guardrails
- Do not claim root cause without evidence.
- Avoid introducing diagnostics that leak secrets or user data.
- Treat production incident commands as high impact and call out safety considerations.
Expected Output
Return an evidence-led diagnosis, remediation path, and verification plan for the .NET issue.