skills.rest
DataDog
DataDogOFFICIAL
Explore all skills by this author →
Website𝕏@datadoghqGitHub

analyze-crash

Parse stack traces and diagnose crashes in the dd-trace-dotnet repository.

570|166|Updated Aug 30, 2017
Search Tags:#debugging#stack trace#dotnet#triage#code investigation#crash analysis
One-click install
npx skills add https://github.com/DataDog/dd-trace-dotnet --skill analyze-crash
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: analyze-crash
Source: https://github.com/DataDog/dd-trace-dotnet/tree/main/.claude/skills/analyze-crash
Command: npx skills add https://github.com/DataDog/dd-trace-dotnet --skill analyze-crash

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineers quickly understand the root cause of software crashes by analyzing stack traces and pinpointing problematic code sections within the dd-trace-dotnet repository.

Core Features & Use Cases

  • Stack Trace Analysis: Parses and classifies stack frames to identify the origin of a crash.
  • Code Contextualization: Locates relevant code in the repository and displays it with surrounding context, highlighting the crash point.
  • Crash Flow Reconstruction: Builds a narrative explaining the sequence of events leading to the crash.
  • Related Code Identification: Finds relevant commits and pull requests to provide historical context.
  • Use Case: When a user reports a crash, this Skill can analyze the provided stack trace to generate a detailed report, enabling developers to efficiently debug and resolve the issue.

Quick Start

Use the analyze-crash skill to analyze the following stack trace: <paste-stack-trace>

Frequently Asked Questions about analyze-crash

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

FAQPage Schema
How do I analyze a dotnet stack trace to find the root cause of a crash?▼

To analyze a dotnet stack trace, parse the stack frames to locate the crash origin, display the surrounding code context, reconstruct the crash flow, and identify related commits for comprehensive triage.

What is the best way to debug a crash in the dd-trace-dotnet repository?▼

The best way to debug a crash in dd-trace-dotnet is to analyze the stack trace data to pinpoint problematic code sections, reconstruct the sequence of events, and review related pull requests for historical context.

Can I identify related commits and pull requests from a stack trace during crash analysis?▼

Yes, during crash analysis you can identify related commits and pull requests by parsing the stack frames, locating the corresponding code snippets, and matching them against the repository's historical changes for comprehensive triage.

Does this crash analysis approach work for any .NET stack trace or only for dd-trace-dotnet?▼

This crash analysis approach specifically diagnoses software crashes within the dd-trace-dotnet repository, systematically parsing stack frames and locating relevant code snippets tailored to that specific codebase.

How does stack trace parsing help with code investigation and triage?▼

Stack trace parsing helps with code investigation by systematically classifying stack frames, locating relevant code with GitHub links, reconstructing the crash flow, and providing the historical context needed for efficient triage.

Why should I use a dedicated tool for dotnet crash analysis instead of manually reading stack frames?▼

Using a dedicated tool for dotnet crash analysis saves time by automatically parsing stack frames, displaying relevant code snippets with context, and linking to related commits, which prevents manual errors during triage.

Related Skills

Explore More Software Engineering Skills→
MCCTeamMCCTeam
2.1k

csharp-dotnet-cli-optimization

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

Official
Advanced
imbue-aiimbue-ai
401

create-fixmes

Insert FIXME comments into code for listed issues.

Official
Intermediate
anxiety135790anxiety135790

node-inspect-debugger

Attach the Node.js inspector to pause execution and inspect stack frames, scopes, and expressions.

Community
Advanced
dotnetdotnet
13

ci-crash-dump

Identify crashed Helix work items and retrieve crash artifacts from dotnet CI runs.

Official
Advanced