crashlytics-triage

Triages Firebase Crashlytics crashes for Meshtastic-Android by version and dispatches parallel investigator agents.

1.8k|511|Updated Jan 20, 2020
One-click install
npx skills add https://github.com/meshtastic/Meshtastic-Android --skill crashlytics-triage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: crashlytics-triage
Source: https://github.com/meshtastic/Meshtastic-Android/tree/main/.claude/skills/crashlytics-triage
Command: npx skills add https://github.com/meshtastic/Meshtastic-Android --skill crashlytics-triage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually sifting through Firebase Crashlytics to figure out what is crashing in the latest Meshtastic-Android release is slow and error-prone, especially when version filter strings must match exact display names. This Skill automates the sweep so you get a clear verdict on build health without hand-building filters or reading raw stack traces.

Core Features & Use Cases

  • Correct version filtering: Queries topVersions first to obtain the exact "X.Y.Z (versionCode)" display name, cross-referencing GitHub releases to identify production builds.
  • Parallel crash investigation: Fans out one crash-investigator subagent per top issue concurrently, each producing a root-cause hypothesis and fix area.
  • Distilled verdict table: Returns a summary mapping each issue to crash counts, root cause, status (NEW / known-fixed-residual / regression), and hotfix vs. next-release recommendation.
  • Use Case: Ask "is build 29321034 healthy?" and receive a triage table of the top crashes for that version with status classifications, instead of manually clicking through the Crashlytics console.

Quick Start

Ask the assistant to triage Crashlytics for the latest Meshtastic-Android release and report whether the build is healthy.

Frequently Asked Questions about crashlytics-triage

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

FAQPage Schema
How do I triage Firebase Crashlytics crashes for an Android release?

Query the topVersions report first to get the exact version display name, then fetch topIssues filtered to that version. Investigate each top issue for root cause and status, and summarize results in a verdict table with crash counts and fix areas.

Why does my Crashlytics version filter match nothing?

The version filter must use the exact display name format "X.Y.Z (versionCode)" returned by the topVersions report. Hand-built filter strings silently match nothing, so always pull the display name from the report first.

How do I know which Crashlytics versionCode shipped on the production track?

The topVersions report does not indicate release tracks, so map candidate versionCodes to GitHub releases using gh release list, since release names embed the versionCode. Never compute versionCodes by hand arithmetic.

When should I use Crashlytics versus Datadog RUM for error investigation?

Crashlytics is the low-volume real-crash signal for the Android app, while Datadog RUM captures high-volume logged errors. Use Crashlytics triage for actual crashes and the Datadog RUM investigator for logged error patterns.

Can I investigate a single known Crashlytics issue instead of a full sweep?

Yes, for a single known issue id you should dispatch the crash-investigator agent directly rather than running the full triage sweep. The sweep is intended for broad questions like what is crashing or whether a build is healthy.