What problem does it solve? Debugging HarmonyOS apps at runtime is hard when crashes, white screens, jank, or network failures leave no obvious trace. This Skill provides a structured workflow for capturing and filtering device logs, locating crash stacks, and verifying fixes with evidence instead of guesswork. ## Core Features & Use Cases - hilog Log Mastery: Covers log levels (DEBUG through FATAL), ArkTS hilog printing with public/private formatting, and filtering by tag, regex, or level via hdc shell hilog. - Device Log Capture: Uses dcli__list_devices, dcli__get_device_logs, and dcli__run_app to build, install, launch, and collect logs from real devices and emulators. - Crash & Runtime Triage: Step-by-step flows for locating FATAL/ERROR stacks, mapping ArkTS exception line numbers to src/main/ets source, and diagnosing common causes like null dereferences, missing permissions, and unregistered routes. - Use Case: Your app crashes on launch after a code change. Use this Skill to reinstall via dcli__run_app, filter logs by your app tag and ERROR level, find the ArkTS stack trace, and trace it back to a missing entry in main_pages.json. ## Quick Start Use the hmos-debug-logs skill to capture device logs for my app, filter for FATAL and ERROR entries, and help me locate the crash cause.
