rnd-automotive-issue-analyzer

Analyze Android Automotive system issues to identify root causes.

110|19|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/chendongqi/OPB-Skills --skill rnd-automotive-issue-analyzer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rnd-automotive-issue-analyzer
Source: https://github.com/chendongqi/OPB-Skills/tree/main/skills/rnd-automotive-issue-analyzer
Command: npx skills add https://github.com/chendongqi/OPB-Skills --skill rnd-automotive-issue-analyzer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

智能座舱系统问题分析专家 - Android车载系统问题诊断与根因定位。帮助快速定位显示异常、系统稳定性、性能、功能以及跨系统协同等问题的根本原因,并提供可执行的解决方案。

Core Features & Use Cases

  • 整合多源日志并构建事件时间线,便于定位问题起点和传播链
  • 跨Android、QNX、MCU等系统的根因定位与证据链分析
  • 提供面向车载场景的系统化诊断方法论与工作流

Quick Start

Describe the issue and logs for an Android Automotive problem to trigger a guided root-cause analysis.

Frequently Asked Questions about rnd-automotive-issue-analyzer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I diagnose Android automotive system crashes and find the root cause?

Android automotive system root cause analysis uses multi-source log correlation, event time-line reconstruction, and 5Why causality to identify crash origins across Android, QNX, and MCU environments. It outputs confidence-scored conclusions for display, stability, and performance issues.

What is the best way to analyze cross-system coordination issues between Android Automotive and QNX?

Cross-system coordination analysis correlates logs across Android Automotive, QNX, and MCU layers to build a unified event timeline. It traces issue propagation chains across system boundaries to pinpoint the origin of interaction failures.

Can I use this log analysis workflow for performance and display issues in car systems?

Yes, this car-system log analysis workflow applies to display anomalies, performance degradation, stability crashes, and functionality defects. It structures multi-source log correlation to isolate the specific subsystem causing the observed issue.

How to start a structured root-cause analysis for an Android Automotive problem?

Start structured root-cause analysis by describing the automotive issue and providing relevant logs. The workflow guides through event time-line reconstruction, multi-source correlation, and 5Why causality analysis to produce evidence-backed conclusions.

Does Android automotive issue diagnosis require logs from all subsystems?

Android automotive issue diagnosis benefits from logs across Android, QNX, and MCU subsystems for comprehensive cross-system correlation, but analysis can begin with available logs and scale as additional sources are integrated into the timeline.

Why does my Android Automotive display issue require cross-system log analysis?

Display issues in Android Automotive often stem from cross-system coordination failures between Android, QNX, and MCU layers. Single-system logs miss the propagation chain, but multi-source correlation reconstructs the event timeline to reveal the actual origin.