debug-crash-live

Correlate Crashlytics crash data with source code to diagnose production issues.

11|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/satanyakiv/NutriSport --skill debug-crash-live
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug-crash-live
Source: https://github.com/satanyakiv/NutriSport/tree/main/.claude/skills/debug-crash-live
Command: npx skills add https://github.com/satanyakiv/NutriSport --skill debug-crash-live

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pull live crash data from Firebase Crashlytics via MCP, correlate with source code, and generate an analysis report with proposed fix.

Core Features & Use Cases

  • Live crash data pull via MCP and Crashlytics
  • Stacktrace-to-source mapping to identify modules and architectural layers
  • Root-cause classification and suggested fixes
  • Cross-reference with Tracey dumps when available and merge user-journey context
  • Produce annotated issue summaries with recommended remediation steps

Quick Start

Run a live crash analysis on the latest production data to identify top issues and proposed fixes.

Frequently Asked Questions about debug-crash-live

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

FAQPage Schema
How do I diagnose production crashes by correlating Crashlytics data with source code?

To diagnose production crashes, this Skill pulls live Crashlytics data via MCP and maps stacktraces to your local codebase, identifying specific modules and architectural layers. It then classifies the root cause and produces an annotated report with suggested fixes.

What do I need to map stacktraces to source files and modules for root-cause analysis?

For mapping stacktraces to source files, you need MCP access to Firebase Crashlytics data and a mapped local codebase. These prerequisites allow the Skill to resolve stack frames to specific source files and generate accurate root-cause classifications.

Can I cross-reference Crashlytics stacktraces with Tracey dumps to understand user journeys?

Yes, you can cross-reference Crashlytics stacktraces with Tracey dumps. When Tracey dumps are available, the Skill merges this user-journey context with the crash data to provide a more comprehensive annotated issue summary.

Does this crash analysis tool work without MCP access to Firebase Crashlytics?

No, MCP access to Firebase Crashlytics is a required dependency. The Skill relies on this MCP integration to fetch live crash data, list issues, and pull detailed crash reports for stacktrace correlation.

What is the best way to analyze mobile app production crashes and get fix recommendations?

The best way to analyze mobile app production crashes is to run a live crash analysis that fetches top issues from Crashlytics via MCP. This process correlates stacktraces with your source code to classify root causes and output annotated summaries with recommended remediation steps.