Debug Crash
- 1 installs
- Updated March 19, 2026
- c0dev0id/awaytogo
debug-crash is a Claude skill that reads Android crash and app logs, correlates the stack frames with Kotlin source, and identifies the root cause of the most recent crash or ANR.
About
This skill reads a project's crash.log and app.log files, finds the most recent crash, exception, or ANR, and extracts the full stack trace. It maps each frame belonging to the app package to its Kotlin source file and reads the surrounding lines to identify the root cause. A developer uses it when triaging an Android crash to get the failing line and a minimal fix.
- Reads log/crash.log and log/app.log to find the most recent crash or ANR
- Maps de.codevoid.aWayToGo stack frames to Kotlin source files and line numbers
- States a one-sentence root cause and suggests a minimal code fix
Debug Crash by the numbers
- 1 all-time installs (skills.sh)
- Ranked #489 of 596 Debugging skills by installs in the Skillselion catalog
- Data as of Jul 8, 2026 (Skillselion catalog sync)
debug-crash capabilities & compatibility
- Capabilities
- crash triage · stack trace analysis · log analysis · debugging
- Use cases
- debugging
What debug-crash says it does
Read log/crash.log and log/app.log, correlate stack frames with Kotlin source, and identify the root cause of the most recent crash or ANR.
State the root cause in one sentence.
Suggest the minimal fix (code, not prose).
npx skills add https://github.com/c0dev0id/awaytogo --skill debug-crashAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1 |
|---|---|
| Last updated | March 19, 2026 |
| Repository | c0dev0id/awaytogo ↗ |
What it does
Correlate a captured Android crash or ANR log with Kotlin source to find the failing line and a minimal fix.
Who is it for?
Triaging the most recent crash or ANR in a Kotlin Android project that logs to log/crash.log.
Skip if: Diagnosing issues with no captured logs, since it says so and reminds the user to run make log-clear then make log first.
When should I use this skill?
After reproducing an Android crash or ANR and capturing log/crash.log and log/app.log via make log.
What you get
A one-sentence root cause, the responsible file path and line number, and a minimal code fix.
- root-cause statement
- responsible file path and line number
- minimal code fix
By the numbers
- 6-step diagnosis procedure
Files
Read log/crash.log and log/app.log in the project root (created by make log).
Follow these steps:
1. Find the most recent crash, exception, or ANR in the logs. 2. Extract the full stack trace including the exception type and message. 3. For every frame that belongs to de.codevoid.aWayToGo, map the class name to its source file in app/src/main/java/ and read the lines around the reported line number. 4. State the root cause in one sentence. 5. Show the specific line(s) responsible with their file path and line number. 6. Suggest the minimal fix (code, not prose).
If both log files are empty or absent, say so and remind the user to run make log-clear before reproducing the issue and make log after.
Related skills
Azure DiagnosticsSystematically diagnose and resolve production issues on Microsoft Azure using official Microsoft guidance.495k1.3kAzure MessagingQuickly diagnose and fix connection, authentication, and message-processing failures when using Azure Event Hubs or Service Bus SDKs.483k1.3k
Diagnosing BugsGet a systematic, step-by-step process that surfaces the real root cause instead of guessing at bugs.291k200k
Use My BrowserWhen their agent task requires access to the live browser session, rendered DOM state, authenticated dashboards, localhost apps, or DevTools-selected elements instea269k71
Systematic DebuggingFollow a repeatable four-phase process that forces root-cause discovery before any code changes.210k265k
Safe DebugGet conservative, non-destructive diagnosis of deep learning and agent errors before any code changes are made.185k512