hmos-runtime-fix-skill

Parse the jscrash log with the provided Node scripts to extract error_type, error_message, suspected_file, and top_stack. Then match the error type against the fault pattern references to identify the root cause and apply a minimal fix.

This TypeError means a variable was not the expected object when a property was accessed. Validate the object exists before use, and check API return values, async timing, and default values at the stack-indicated location.

Yes, the Skill can run devecocli log --crash or collect a hilog snapshot from a connected device using the app's bundleName from AppScope/app.json5. If multiple devices are connected, the user must select one first.

Runtime crashes like ReferenceError, TypeError, or BusinessError come from uncaught exceptions that compilation cannot detect, such as uninitialized variables or invalid API parameters. Parse the crash log to find the error type and suspected file before reading code broadly.

Analysis requires a concrete crash anchor such as an error type or stack trace; vague symptom descriptions alone are insufficient. If the log shows no crash signature, better evidence like a fuller log or clearer reproduction steps is needed.