Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From axiom
Parses iOS/macOS crash logs (.ips, .crash, or pasted text) and identifies root cause by extracting exception type, crashed thread, and symbolication status.
How this command is triggered — by the user, by Claude, or both
Slash command
/axiom:analyze-crashThe summary Claude sees in its command listing — used to decide when to auto-load this command
# Analyze Crash Log Launches the **crash-analyzer** agent to parse crash reports and identify the root cause. ## What It Does The agent will: 1. Parse the crash report (JSON .ips or text .crash format) 2. Extract key fields (exception type, codes, crashed thread, frames) 3. Check symbolication status 4. Categorize by crash pattern (null pointer, Swift runtime, watchdog, jetsam, etc.) 5. Generate actionable analysis with specific next steps ## Crash Sources Provide crashes via: - **Pasted text** — Copy/paste the crash report directly - **File path** — `~/Library/Logs/DiagnosticReports/M...
Launches the crash-analyzer agent to parse crash reports and identify the root cause.
The agent will:
Provide crashes via:
~/Library/Logs/DiagnosticReports/MyApp.ips# macOS/iOS Simulator crash logs
~/Library/Logs/DiagnosticReports/*.ips
# Device crash logs (after sync)
~/Library/Logs/CrashReporter/MobileDevice/<DeviceName>/
You can also trigger this agent by saying:
npx claudepluginhub p/charleswiltgen-axiom-claude-plugin-plugins-axiom/crash-reportGenerates crash triage report from Firebase Crashlytics for iOS/Android apps: analyzes fatal errors, stack traces, proposes platform-specific fixes, assigns developers via git, outputs markdown.
/investigatorDiagnoses bugs and incidents through root-cause analysis, gathering evidence before proposing any fix. Triggers on keywords like bug, debug, investigate, or incident.
/engage.crashAnalyzes a native crash to produce validated root cause and empirical exploitability verdict. Uses rr time-travel debugging, coverage reachability, and feasibility profiling.
/stacktrace-analyzeAnalyzes a pasted stack trace to identify root cause, call chain, and actionable fix across multiple languages and runtimes.
/macos-signing-inspectInspects macOS app bundles or binaries for signing and entitlement failures, then explains the minimal fix path. Optionally generates a repair plan.
/smart-debugParses error messages, stack traces, and failure patterns to identify root causes and produce a fix with automated observability steps.