crash-analysis · git:20260506.478f83b · 2026-05-06 · sha256 d41dac525c5b4203

crash-analysis git:20260506.478f83bA

Immutable. This exact content never changes and is served at /api/v1/blob/d41dac525c5b4203.

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_exl3gf62m72yduw7/d41dac525c5b420361c8e6fb2c5587bf0b20336aa020aee809855bdb2272ae39.json

Then /plugin install crash-analysis@markdownregistry-exl3gf62m72yduw7 in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.

---
name: crash-analysis
description: Analyzing core dumps, stack traces, and unhandled exceptions
---

# Crash Analysis Skill

This skill is designed for debugging fatal errors that result in process termination or generic 500 crashes.

## When to use this skill
- When facing segmentation faults, null pointer exceptions, or stack overflows.
- When an application terminates abruptly without graceful error logs.
- When analyzing core dumps or fatal crash reports.

## Guidelines
- **Start at the Source:** Always look at the top/bottom of the stack trace to find the exact line of application code that triggered the failure, ignoring framework-level abstractions if possible.
- **Reproducibility:** Prioritize establishing a reliable reproduction path or writing a fast failing test.
- **State Capture:** Identify what the data state was exactly at the moment of the crash (variables, inputs).