mobile-debug
Skill8 starsChanged 58 days agoMITView on GitHub
Diagnoses build and runtime failures across Flutter, native Android, native iOS, React Native and Kotlin Multiplatform. Covers pub/Dart, Gradle/AGP, Xcode/CocoaPods, Metro, KMP source sets and iOS frameworks, crashes and deep links. Use for failing builds, app launches, stack traces or /reis-mobile:debug.
In this repository27 other files it gives its agents.
- AGENTS.mdAGENTS.md
- mobile-accessibilitySkill
- mobile-analyticsSkill
- mobile-androidSkill
- mobile-architectureSkill
- mobile-authSkill
- mobile-billingSkill
- mobile-ciSkill
- mobile-code-reviewSkill
- mobile-detect-stackSkill
- mobile-firebaseSkill
- mobile-flutterSkill
- mobile-hardwareSkill
- mobile-iosSkill
- mobile-kmpSkill
- mobile-migrationSkill
- mobile-networkingSkill
- mobile-notificationsSkill
- mobile-observabilitySkill
- mobile-offline-syncSkill
- mobile-performanceSkill
- mobile-privacySkill
- mobile-releaseSkill
- mobile-rnSkill
- mobile-securitySkill
- mobile-testSkill
- mobile-ui-uxSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 25
When reis-mobile debug (or /reis-mobile:debug) ran, its area line points at the layer: gradle, manifest, proguard → Android.
- Very specific: line 37
Read-only commands can run: version checks, dependency trees, flutter doctor -v, ./gradlew --version, pod --version, xcodebuild -version.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Mobile Debug
One debugging process for every mobile stack. This file holds how to find a cause; each platform's error signatures and fixes live in its reference.
1. Pick the reference
Choose by the stack and by the layer the error comes from — a Flutter or React Native build often fails inside Gradle or Xcode:
| The failure is in | Read |
| A Flutter app: pub, Dart compilation, generated code, widgets, runtime exceptions | references/flutter.md |
Gradle, the Android build, logcat crashes or ANRs (native Android, or the android/ folder of any app) | references/android.md |
Xcode, signing, CocoaPods, Swift packages or iOS crash logs (native iOS, or the ios/ folder of any app) | references/ios.md |
| A React Native or Expo app: Metro, native modules, JavaScript errors | references/react-native.md |
| Kotlin Multiplatform compilation, source-set or framework integration | references/kotlin-multiplatform.md |
| A deep link, App Link or Universal Link that opens the browser, the wrong screen or crashes (any stack) | references/deep-links.md |
When reis-mobile debug (or /reis-mobile:debug) ran, its area line points at the layer: gradle, manifest, proguard → Android; xcode, signing, cocoapods, spm → iOS; pub → Flutter; metro → React Native.
2. Find the first real error
Build and crash logs bury the cause under cascading failures. Quote the line that starts the failure — the first error:, the What went wrong block, the top of the exception with its Caused by — not the final BUILD FAILED or the last frame. Ask for the full output when the user pasted only the end.
3. Collect versions before theorizing
Most build failures after an upgrade are toolchain mismatches. Read the versions that decide the behavior — the SDK and toolchain versions (the doctor report shows them), wrapper and lock files, build scripts, deployment targets — and quote them in the diagnosis. Check compatibility against the official tables named in the reference; do not state compatibility ranges from memory.
4. Reproduce safely
Read-only commands can run: version checks, dependency trees, flutter doctor -v, ./gradlew --version, pod --version, xcodebuild -version. A build that only compiles can run when the user already ran it or agrees, since it takes time and writes build outputs.
5. Confirm the cause
Tie the cause to evidence: file:line, a version, a build setting or a log line. If two causes are plausible, say what evidence would separate them instead of picking one.
6. Propose, then wait
Answer with:
- Cause — one or two sentences, with the evidence.
- Fix — the minimal change, as a diff or exact commands, in order.
- Side effects — what else the fix changes: a higher minimum Android or iOS version, a Gradle or Kotlin upgrade that CI needs too, pods changing version.
- Verify — the command that failed, run again.
Do not edit files, upgrade dependencies or run commands that change the project, the caches or the machine — flutter clean, pod install, pod repo update, npx expo prebuild --clean, deleting DerivedData, ~/.gradle caches or node_modules — until the user asks you to apply the fix. Then apply it, run the verification and report the result.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.