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.