version: "1.0.0" name: autosar-arxml-bsw-reviewer description: Parse, inspect, and review AUTOSAR Classic ARXML for BSW configuration and integration. Use when Codex needs to analyze .arxml files, extract ECUC modules, resolve AUTOSAR references, validate Com/PduR/CanIf/CanTp/Dcm paths, check Dem/Dcm/NvM/OS configuration, or generate BSW integration review findings.

AUTOSAR ARXML BSW Reviewer

Workflow

1. Identify the user's goal: inventory, extraction, reference resolution, communication path review, diagnostics review, NvM review, OS schedule review, or patch proposal.
2. For DBC/LDF traceability, identify the target ECU before analysis. If the user has not provided it, ask for the ECU name and any known aliases used in each network file.
3. Run scripts/arxml_inventory.py before domain-specific checks unless a current inventory already exists.
4. Run scripts/arxml_extract_ecuc.py when ECUC module configuration is needed.
5. Run scripts/arxml_resolve_refs.py before any cross-module validator.
6. Run scripts/check_can_dbc_traceability.py when the user needs to prove that DBC messages/signals appear in AUTOSAR configuration.
7. Run scripts/check_lin_ldf_traceability.py when the user needs to prove that LDF frames/signals appear in AUTOSAR configuration.
8. For domain checks, load only the relevant reference file:

• Communication paths: references/comm_stack_checks.md
• System services and mode control: references/system_module_checks.md
• Deep system-module semantics: references/system_module_semantic_model.md
• ECUC resource configuration: references/ecuc_resource_configuration.md
• CAN DBC to AUTOSAR traceability: references/can_dbc_traceability.md
• LIN LDF to AUTOSAR traceability: references/lin_ldf_traceability.md
• Signal and message routing: references/signal_and_message_routing.md
• COM to application/RTE interface and computation methods: references/com_application_interface_checks.md
• Runnable trigger sources and RTE events: references/runnable_trigger_checks.md
• Diagnostics: references/diagnostics_checks.md
• CanTp and UDS diagnostic stack: references/cantp_diagnostic_stack_checks.md
• XCP measurement and calibration: references/xcp_configuration_checks.md
• Memory and NvM: references/memory_stack_checks.md
• Memory lifetime estimation: references/memory_lifetime_estimation.md
• OS and scheduling: references/os_schedule_checks.md
• BSW module extraction patterns: references/bsw_module_patterns.md
• Vendor-specific behavior: references/vendor_notes.md

1. Report findings with severity, affected module, evidence path, source file, recommended action, and validation method.

Guardrails

• Treat ARXML as production configuration unless the user says it is a sandbox.
• Never overwrite ARXML directly. Generate patch proposals or review reports.
• Distinguish AUTOSAR-standard findings from vendor-tool assumptions.
• Preserve source file and element path in every finding.
• Prefer deterministic script output over LLM-only reasoning for references, IDs, paths, and timing checks.
• Do not infer message direction from one DBC/LDF file until the target ECU and network-specific aliases are known.

Output Shape

Use this structure:

1. Scope
2. Inputs analyzed
3. Assumptions
4. Findings by severity
5. Affected BSW modules
6. Recommended actions
7. Validation plan
8. Open questions