What problem does it solve? HarmonyOS/OpenHarmony app crashes at the ArkTS/JS layer produce dense faultlogger logs that are hard to interpret, especially when release builds are obfuscated. This Skill turns those raw logs into an evidence-based root cause report with concrete fix suggestions. ## Core Features & Use Cases - Structured crash analysis: Extracts Reason, Error name, Error message, Error code, and Stacktrace fields, then matches them against a three-level JSError fault mode library (TypeError, ReferenceError, OutOfMemoryError, and more). - SourceMap symbolication: Uses the bundled cross-platform hstack tool to deobfuscate release/minified stack traces with sourceMaps.json and nameCache.json, restoring original source file, line, and column positions. - OOM snapshot handoff: When a crash is confirmed as OutOfMemoryError and the user provides rawheap or heapsnapshot files, it automatically chains into the jsleak-analysis Skill to locate suspected leak objects. - Use Case: A developer pastes a faultlogger log showing "TypeError: Cannot read property of undefined" after their app crashes on launch; the Skill identifies the responsible application stack frame, matches the fault pattern, and outputs a full analysis report with repair recommendations. ## Quick Start Ask the AI to analyze your HarmonyOS JS Crash log file with this skill, for example: "Use hmos-jscrash-analysis to analyze this jscrash faultlogger log and tell me the root cause."
