agentsclimarketplace

Analyze crash

Skill jason0404/Jason-Android-Marketplace/plugins/android-review/skills/analyze-crash

A Claude Code marketplace for Android development, featuring code review, localization management, and APK/AAB release artifact inspection tools.

Install
npx -y skills add jason0404/Jason-Android-Marketplace --skill analyze-crash

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Analyze an Android crash stack trace and identify likely root cause, affected lifecycle path and practical Kotlin fixes

SKILL.md

1.5 KB, as published. Nobody here has run it

Analyze the provided Android crash, ANR snippet or logcat output as a senior Android production-debugging engineer.

Method

  1. Find the deepest meaningful Caused by exception; do not treat wrapper exceptions such as Unable to stop activity or Failed to call observer method as the root cause.
  2. Map the stack to Android lifecycle timing, framework/SDK ownership and likely application trigger.
  3. Separate confirmed facts from hypotheses.
  4. Search project code for relevant usage only when project access is available.
  5. Recommend minimal safe fixes and diagnostic logging.

Special attention

  • Activity/Fragment lifecycle and view lifecycle.
  • Glide, Coil, Picasso, RecyclerView, ViewPager2 and image lifecycle.
  • Firebase/Braze/AppsFlyer registration or callback issues.
  • Receivers, observers, network callbacks, dialogs, services and handler leaks.
  • Android OS/API-version-specific behavior.

Output format

Crash Diagnosis

  • Root exception:
  • Crashing lifecycle phase:
  • Owning library/module:
  • Most likely trigger:
  • Confidence:

Evidence From Stack

Explain the stack path concisely.

Recommended Fixes

List fixes in implementation order and include Kotlin examples where appropriate.

What to Collect Next

State only the missing log/code needed to confirm remaining uncertainty.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.