Crash Debugging

Crash Debugging is a Quality skill for Claude Code, published by conorluddy in xclaude-plugin.

182 stars17 forkson conorluddy/xclaude-pluginAdded 2026/09/07Repository updated 2026/02/07

agenticagentic-workflowclaudeclaude-codeclaude-code-pluginclaude-mcpclaude-pluginsclaudecodecontext-engineeringdeveloper-toolsiosllmmcpmcp-serverpluginswifttoolingxcodexcodebuild

Install in seconds

Install Crash Debugging

Copy Crash Debugging into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.

terminal

npx degit https://github.com/conorluddy/xclaude-plugin/tree/main/skills/crash-debugging ~/.claude/skills/crash-debugging

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/conorluddy/xclaude-plugin.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file: skills/crash-debugging/SKILL.md in conorluddy/xclaude-plugin
Installs to: ~/.claude/skills/crash-debugging
Collection: One of 8 skills cataloged from this repository
Category: Quality — 1817 skills

What Crash Debugging does

Crash Debugging analyzes iOS crash logs, symbolicates stack traces with dSYM files, and helps identify root causes. Use it when investigating app crashes, TestFlight reports, or unsymbolicated crash reports.

Crash Debugging is cataloged under Quality on DirSkills. Crash Debugging comes from a repository tagged agentic, agentic-workflow, claude, claude-code and claude-code-plugin.

Documentation

README

Excerpt

Crash Debugging Skill

Comprehensive guide to iOS crash analysis and debugging

Quick Reference

Task	Tool/Command	Location
View crash logs	Console.app	macOS Application
Retrieve simulator crashes	~/Library/Logs/DiagnosticReports/	File system
Symbolicate crash	atos	Command line
Find dSYM files	Xcode Organizer / DerivedData	Xcode
Analyze crash type	Stack trace patterns	Crash log

Overview

Crash debugging transforms cryptic crash logs into actionable insights. This skill covers:

Retrieving crash logs from simulators and devices
Understanding crash log structure
Symbolicating stack traces for readable function names
Identifying common crash patterns
Determining root causes

This is the opening of the README. Read the full README on GitHub.

Frequently asked about Crash Debugging

What else does conorluddy publish alongside Crash Debugging?
Crash Debugging is one of 8 skills that DirSkills catalogs from conorluddy/xclaude-plugin, the repository it ships in. Its siblings there include Accessibility Testing, Performance Profiling and Simulator Workflows. Each one is a separate skill with its own page in this directory, installs the same way Crash Debugging does, and is maintained by conorluddy in that same repository. The rest of the collection is listed on the conorluddy/xclaude-plugin page.
How does Crash Debugging compare to other Quality skills?
Crash Debugging ranks #1666 by stars among the 1817 Quality skills in this catalog. The most-starred ones next to it are Benchmark, Benchmark Optimization Loop and API Design Patterns. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Crash Debugging against them. Open each page to compare what they document and how they install.