ivx-crashlytics

Capture native crashes, uncaught exceptions, and ANR events for IntelliVerseX SDK games.

1|4|Updated Jan 12, 2026
One-click install
npx skills add https://github.com/intelli-verse-x/Intelli-verse-X-SDK --skill ivx-crashlytics
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ivx-crashlytics
Source: https://github.com/intelli-verse-x/Intelli-verse-X-SDK/tree/main/.cursor/skills/ivx-crashlytics
Command: npx skills add https://github.com/intelli-verse-x/Intelli-verse-X-SDK --skill ivx-crashlytics

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill centralizes crash reporting, error tracking, and diagnostics for games built with the IntelliVerseX SDK, removing the manual burden of collecting stack traces, player context, and breadcrumbs across platforms so teams can quickly triage and resolve issues.

Core Features & Use Cases

  • Automatic capture of unhandled exceptions, native crashes, non-fatal errors, and ANR events with device, app, session, and game-state metadata.
  • Breadcrumb trails and custom breadcrumbs to reconstruct sequences leading to failures, plus crash grouping via stack fingerprinting to prioritize fixes.
  • Multiple backend options including Nakama for self-hosting and integrations with Sentry, Firebase Crashlytics, and Backtrace, plus offline queuing, screenshot attachments, and webhook alerts to Slack or Discord.
  • Use Case: After a release causes a crash spike, identify the top crash group, review attached breadcrumbs and device metadata to reproduce the issue, then configure webhook alerts for regressions.

Quick Start

Initialize IVXCrashlytics in your project, select a backend (Nakama, Sentry, or Firebase), and enable breadcrumb capture to start collecting crash reports.

Frequently Asked Questions about ivx-crashlytics

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I capture native game crashes and ANR events across multiple platforms?

Crash grouping uses stack trace fingerprinting to consolidate duplicate crash reports into prioritized groups. Breadcrumb trails and custom breadcrumbs are captured to reconstruct the exact sequence of events leading up to game failures.

Can I send crash reports to Sentry, Firebase, or a Nakama backend?

Crash reports can be stored in Nakama for self-hosting or forwarded to external backends including Sentry, Firebase Crashlytics, and Backtrace. You simply select your preferred backend during initialization to route diagnostic data accordingly.

How do I alert my team about crash spikes or regressions in real-time?

Webhook alerting sends real-time crash spike and regression notifications to Slack or Discord. You configure webhooks to monitor top crash groups, enabling teams to triage and resolve issues immediately after a release.

How are offline crash reports queued and retried during gameplay?

Offline queuing stores crash reports locally when network connectivity is lost during gameplay. The system automatically retries sending queued reports, complete with screenshot attachments and metadata, once the connection is restored.