← ClaudeAtlas

xcsymlisted

Symbolicate and triage iOS/macOS crash reports (.ips, MetricKit, legacy .crash, Xcode Organizer .xccrashpoint) via the `xcsym` CLI. Use when given a crash file to diagnose, when TestFlight/App Store Connect crashes need triage, when a crash comes back unsymbolicated, or when asked what kind of crash something is.
patrickserrano/lacquer · ★ 1 · Data & Documents · score 67
Install: claude install-skill patrickserrano/lacquer
# xcsym — Crash Symbolication `xcsym` parses a crash report end-to-end (detect format → discover dSYMs → symbolicate via `atos` → categorize into a `pattern_tag`) and emits token-lean JSON, so triage is one call instead of the manual `atos`/dSYM-hunting dance. Use it instead of raw `atos` or `symbolicatecrash` for any `.ips`, MetricKit, `.crash`, or `.xccrashpoint` input — this fleet has no other crash-symbolication path today; `native-app-profiling`/`swiftui-expert-skill` cover live Instruments profiling, not post-mortem crash files. ## Resolving the binary `xcsym` is not bundled with FlowDeck or RocketSim and ships no Homebrew formula or GitHub release — it's a zero-dependency Go module distributed as source inside [CharlesWiltgen/Axiom](https://github.com/CharlesWiltgen/Axiom) (`tools/xcsym/`, MIT). Resolve it once per machine: 1. `command -v xcsym` — if found, use it. 2. If not found, stop and tell the user to build it: `git clone --depth 1 https://github.com/CharlesWiltgen/Axiom /tmp/axiom-src && cd /tmp/axiom-src/tools/xcsym && go build -o xcsym . && sudo mv xcsym /usr/local/bin/` (or any directory on `PATH`). Do not attempt this yourself unless the user has already agreed to installing new tooling. Don't confuse this with the full Axiom Claude Code plugin — this fleet deliberately did not adopt that (see `docs/references.md`); only the standalone `xcsym` binary is in use here. ## Core workflow `crash` is the default entry point — it does everything in one call: