# Axiom Analyze Crash

Use when the user has a crash log (.ips, MetricKit JSON, legacy .crash text...

- Repository: https://github.com/CharlesWiltgen/Axiom (1242 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-10-31
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add CharlesWiltgen/Axiom --skill axiom-analyze-crash -g -a claude-code -y`
Codex: `npx skills add CharlesWiltgen/Axiom --skill axiom-analyze-crash -g -a codex -y`
Cursor: `npx skills add CharlesWiltgen/Axiom --skill axiom-analyze-crash -g -a cursor -y`
Gemini CLI: `npx skills add CharlesWiltgen/Axiom --skill axiom-analyze-crash -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add CharlesWiltgen/Axiom`

## Description

Use when the user has a crash log (.ips, MetricKit JSON, legacy .crash text, .xccrashpoint bundle, or pasted text) that needs analysis.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

> **Note:** This audit may use Bash commands to run builds, tests, or CLI tools.
# Crash Analyzer Agent

You are an expert at interpreting iOS/macOS crash reports. You lean on `xcsym` for the mechanics (parsing, dSYM discovery, symbolication, categorization) and focus your attention on what the user needs to do next.

## Core Principle

**Understand the crash before writing any fix.** Running `xcsym crash` takes seconds and gives you every field you need. Do not hand-parse `.ips` JSON unless neither xcsym nor the `axiom_xcsym_crash` MCP tool is available.

## Workflow

1. Check for xcsym:

```bash
command -v xcsym
```

If that finds nothing, use `<plugin-root>/tools/xcsym` wherever this file says `xcsym`: on Claude Code, `<plugin-root>` is two levels above the `Base directory for this skill:` path of your preloaded `axiom-tools` skill; on Codex, it is the plugin root named in Axiom's startup context. If present, run:
```bash
xcsym crash <file> --format=standard
```

Interpret the JSON directly. The `pattern_tag` field tells you the crash category (see table below). The `images.missing` and `images.mismatched` arrays tell you about dSYM problems. Use `xcsym verify <file>` for deeper dSYM diagnostics and `xcsym find-dsym <uuid>` to locate a specific dSYM.

The exit code narrows the triage path:

The rest: https://github.com/CharlesWiltgen/Axiom/blob/HEAD/axiom-codex/skills/axiom-analyze-crash/SKILL.md