{"enrichment":{"faq":[{"a":"axiom-analyze-crash analyzes a single iOS or macOS crash log to identify the root cause and recommend a fix. It decodes stack traces, classifies crash patterns (force-unwrap, memory issues, concurrency problems, etc.), and surfaces the underlying failure so you can address it quickly.","q":"What can axiom-analyze-crash do with an iOS crash log?"},{"a":"axiom-analyze-crash symbolicates crash frames and resolves dSYM UUID mismatches. It matches raw memory addresses in your crash report to human-readable function names and source locations, then diagnoses missing or mismatched dSYM files that prevent proper symbolication.","q":"How does axiom-analyze-crash symbolicate crash files?"},{"a":"Yes. axiom-analyze-crash interprets exception codes and termination reasons in crash reports, including watchdog violations (like 0x8BADF00D), jetsam OOM crashes, and main thread checker violations. It translates these codes into actionable diagnostics.","q":"Can axiom-analyze-crash interpret exception codes and termination reasons?"},{"a":"axiom-analyze-crash performs crash pattern identification and root cause analysis on your app's crash logs. It cuts through the stack trace to reveal whether the failure stems from a memory issue, threading problem, framework conflict, or other underlying cause, then recommends targeted solutions.","q":"What caused my app to crash\u2014how does axiom-analyze-crash help?"},{"a":"axiom-analyze-crash accepts .ips crash report files and parses them to extract diagnostic data. Feed it your iOS crash dump or macOS crash log, and it will symbolicate frames, classify the crash pattern, and interpret exception codes to help you understand and fix the problem.","q":"How do I use axiom-analyze-crash to parse .ips crash reports?"},{"a":"axiom-analyze-crash is released under the MIT license, allowing free use, modification, and distribution in both open-source and commercial projects.","q":"What is axiom-analyze-crash's license?"}],"shadow_tags":["crash-triage","symbolication-guide","dsym-diagnostics","pattern-classification","exception-analysis","memory-safety","thread-safety","termination-codes","frame-inspection","build-mismatch"],"summary_rewrite":"axiom-analyze-crash helps developers quickly decode crash logs from iOS and macOS apps, surfacing the underlying failure and recommending targeted solutions. Built on deep Apple platform expertise, it cuts through stack traces to reveal what actually went wrong\u2014whether it's a memory issue, threading problem, or framework conflict\u2014so you can fix it fast."},"files":[{"bytes":12146,"path":"axiom-codex/skills/axiom-analyze-crash/SKILL.md","sha256":"decec8f842b20cbe42dcc22a4125e5da71ea81c942a09c1c82e79bd10a70f1ca","url":"https://skillfed.io/files/CharlesWiltgen/Axiom/axiom-analyze-crash/b4c2d940/SKILL.md"}],"id":"CharlesWiltgen/Axiom/axiom-analyze-crash","links":{"html":"https://skillfed.io/CharlesWiltgen/Axiom/axiom-analyze-crash","md":"https://skillfed.io/CharlesWiltgen/Axiom/axiom-analyze-crash.md","repo":"https://github.com/CharlesWiltgen/Axiom"},"meta":{"agents_supported":[],"first_seen":"2026-07-28","forks":81,"language":"Go","last_updated":"2026-07-27","license":"MIT","name":"axiom-analyze-crash","publisher":"CharlesWiltgen","stars":1095},"relations":{"similar":[{"id":"CharlesWiltgen/Axiom/axiom-analyze-triage"},{"id":"managedcode/dotnet-skills/apple-crash-symbolication"},{"id":"dotnet/skills/apple-crash-symbolication"},{"id":"CharlesWiltgen/Axiom/axiom-analyze-test-failures"},{"id":"CharlesWiltgen/Axiom/axiom-debug-tests"},{"id":"CharlesWiltgen/Axiom/axiom-test-simulator"},{"id":"CharlesWiltgen/Axiom/axiom-shipping"},{"id":"conorluddy/xclaude-plugin/crash-debugging"},{"id":"CharlesWiltgen/Axiom/axiom-performance"},{"id":"CharlesWiltgen/Axiom/axiom-profile-performance"}]},"slug":{"owner":"CharlesWiltgen","repo":"Axiom","skill":"axiom-analyze-crash"},"version":"b4c2d940"}