autonomousguy

MISRA C:2025 expert that operates in two modes: (1) Review — scan existing C code for violations across all ~223 guidelines (22 directives + ~201 rules), report findings with rule IDs, corrected code, and deviation justification templates; (2) Develop — generate new C functions, modules, or data structures that are MISRA-compliant from the first line, applying the essential type model, safe control flow, and banned-construct avoidance from the start. Covers C:2023 base (C:2012 + Amd1 security + Amd2/Amd3 C11/C18 + Amd4 multithreading) plus the four C:2025 additions (Rules 8.18, 8.19, 11.11, 19.3), Rule 15.5 disapplication, and 69 refined guidelines. Reviews the whole translation unit it can see (not only the lines flagged), returns decision-ready findings with a built-in self-check and explicit confidence/gaps, and can optionally emit a self-contained HTML report under analysis/.

ISO 26262 functional-safety expert that operates in two modes: (1) HARA / ASIL determination — enumerate hazardous events from item malfunctions × driving situations, rate Severity (S0–S3), Exposure (E0–E4), Controllability (C0–C3), look up ASIL from ISO 26262-3:2018 Table 4, and produce a HARA report with Safety Goals; (2) Safety Goals & FSC — translate hazardous events and ASIL into well-formed Safety Goals with safe state, Fault Tolerant Time Interval (FTTI = FDTI + FRTI), Emergency Operation Time Interval (EOTI), and high-level Functional Safety Requirements allocated to system elements. Both modes cover ASIL decomposition applicability per Part 9 §5. Works the full item in a single pass and returns decision-ready safety artefacts with a built-in self-check and explicit confidence/gaps.

AUTOSAR BSW expert. Defaults to Classic AUTOSAR (BSW/MCAL/RTE, static config, C, AUTOSAR OS) and operates in six modes: (1) BSW configuration — Com, NvM, Dem, Dcm, Os, MemIf with dependency chain and EB Tresos / DaVinci container paths; (2) ARXML debugging — classify, locate, and fix consistency errors with a corrected fragment and prevention rule; (3) RTE generation troubleshooting — diagnose generator failures across pre-gen, contract, implementation, and post-gen build phases; (4) COM stack debugging — layer-walk CanDrv → CanIf → PduR → Com → RTE for missing, wrong, stale, or intermittent CAN signals; (5) Boot, NVM & power — EcuM/BswM startup and shutdown, bootloader / UDS reprogramming, NvM/Fee/Ea storage, sleep/wakeup, partial networking; (6) Communication protocol — CAN / CAN FD, LIN, CanTp, PduR gateway, ComM/Nm, UDS (ISO 14229), SOME/IP, DoIP. Handles Adaptive AUTOSAR (ara:: clusters) when the input names ara::com, ara::exec, POSIX, or manifests, plus legacy bring-up behind MCAL/CDD interfaces.

AUTOSAR SWC expert. Defaults to Classic AUTOSAR (SWCs, RTE, ARXML, C) and operates in five modes: (1) Component design — decompose a feature into SWC types, define port interfaces, specify runnables and ExclusiveAreas, produce a plain-text composition diagram; (2) Interface definition — SenderReceiver / ClientServer / ModeSwitch / Parameter interfaces with correct AUTOSAR data types, scaling, InitValues, and AliveTimeout, as an ARXML sketch plus C typedef header; (3) SWC development — production-ready SWC skeleton (.c + .h + ARXML) with correct RTE API calls and MISRA-aligned style; (4) Diagram generation — plain-text component / sequence diagrams and ASCII state machines with AUTOSAR layer boundaries and ASIL notes; (5) Integration review — audit C and ARXML for port-interface alignment, RTE API naming, runnable-to-event mapping, and MCAL abstraction violations. Targets EB Tresos and Vector DaVinci. Handles Adaptive AUTOSAR (ara::com proxy/skeleton services) and legacy bring-up in smallest safe steps.

Change-management expert that operates in two modes: (1) CR analysis — take a change request / ECN / feature brief and produce affected-element list, ASIL impact, implementation plan with owner hints and complexity, test plan delta, and integration risks; (2) Impact analysis — trace a specific change through every layer (SWCs, BSW modules, ARXML interfaces, requirements, tests, safety artefacts), distinguishing direct impacts (must change) from indirect impacts (must review or retest), and recommend a regression scope (Minimal / Targeted / Full). Applies ASPICE SWE.6 and ISO 26262-6 §7.4 / -8 §8.4 change practices. Traces the full ripple in a single pass, returns a decision-ready plan/scope with a built-in self-check and explicit confidence/gaps, and can optionally emit a self-contained HTML report under analysis/.

Senior embedded-engineer code review. Defaults to Classic AUTOSAR embedded C and covers two concerns: (1) Correctness review — integer overflow, volatile correctness, ISR/task race conditions, stack usage, dynamic memory, control flow, AUTOSAR/ISO 26262 readiness, with findings rated Critical/Major/Minor; (2) Naming review — AUTOSAR Classic conventions for modules, SWC types, port names, runnables, C identifiers, typedefs, macros, and enumerations, aligned with MISRA Rule 5.x identifier uniqueness. Audits existing code and generates correctly-named identifiers for new work. Handles Adaptive AUTOSAR C++14+ when the input is C++ or names ara::, reviewing RAII, exceptions vs ara::core::Result, smart pointers, and AUTOSAR C++14 / MISRA C++:2023 naming. A third focus, legacy modernization assessment, proposes the smallest safe steps toward a MISRA-conformant, MCAL-abstracted, unit-tested state. Returns decision-ready findings with a built-in self-check and can emit a self-contained HTML report under analysis/.

Senior embedded debugging expert. Defaults to Classic AUTOSAR on ARM Cortex-M/R targets and operates in two modes: (1) Problem-report triage — take a field PR / bug ticket and produce symptom classification, affected-element mapping, ranked hypotheses, data-collection plan, and step-by-step investigation; (2) Targeted fault debugging — accept a specific fault signature (watchdog reset, HardFault, wrong output value, Dem event, stack overflow, AUTOSAR OS error, linker hang) and give concrete debugging steps with GDB/TRACE32 commands, code patterns to inspect, ranked root-cause candidates, and a minimal reproduction strategy. Covers AUTOSAR OS (EB Tresos, Vector) and common BSW/RTE failure modes. Handles Adaptive AUTOSAR when the input names POSIX/Linux/QNX, ara::, C++, segfault, core dump, or Execution Management. Returns decision-ready ranked hypotheses with a built-in self-check and can emit a self-contained HTML report under analysis/.

Requirements-engineering expert that operates in three modes: (1) Elicitation — extract atomic, testable requirements from briefs, meeting notes, or system specs using EARS notation, with full attribute set (ID, type, priority, ASIL, verification method, source), flagging ambiguities as open questions; (2) Refinement — detect requirement defects (vague qualifiers, compound statements, implementation prescription, untestability, missing attributes) and rewrite each as a specific, measurable, EARS-formatted statement with documented assumptions; (3) Traceability — build bidirectional matrices (SYS-REQ → SW-REQ → design → test), detect orphaned requirements / design elements / tests, and flag safety gaps where ASIL-tagged requirements have no test coverage (ISO 26262-6 §9 violation). Aligned with EARS, SMART, ISO 26262-6, and ASPICE SWE.1/SWE.6 practices. Covers the whole input in a single pass and returns decision-ready requirements with a built-in self-check and explicit confidence/gaps.

Embedded test-design expert that operates in two modes: (1) Unit-test generation — analyse a C function for decisions and conditions, produce test cases achieving MC/DC coverage (required for ASIL-C/D), add boundary and error-path tests, provide RTE/BSW stub declarations, and output a coverage matrix; (2) Boundary value analysis — compute MIN, MIN+1, nominal, MAX-1, MAX, and out-of-range points for every typed numeric parameter (uint8/sint8/uint16/sint16/uint32/sint32 and fixed-point), and identify overflow, wrap-around, truncation, and sign-extension risks with triggering inputs and safe fixes. Test output is compatible with Unity, CppUTest, and VectorCAST patterns. A third use, characterization testing, pins the existing behaviour of legacy code before a modernization step so equivalence can be proven after the change. Returns decision-ready, self-checked test sets with explicit coverage gaps stated.

First-run skill that walks the entire repository, auto-detects Classic vs Adaptive AUTOSAR, and maps it accordingly. For Classic (default): identifies features and SWCs and documents referenced requirement IDs (SW-REQ-*, REQ-*, FSR-*, SYS-REQ-*), port interfaces (S/R, C/S, Mode Switch, Parameter), dependencies on other SWCs and BSW modules (Com, NvM, Dem, Dcm, IoHwAb, Os), and concrete RTE API calls (Rte_Read_*, Rte_Write_*, Rte_Call_*, Rte_IRead_*, Rte_IWrite_*). For Adaptive (C++14, POSIX, ara::): identifies Adaptive Applications, ara::com service interfaces, ara:: functional-cluster usage, and manifests. Also captures repository structure, ASIL zones, signal/service flow, and architectural concerns. Writes findings to .autonomousguy/CODEBASE_MAP.md so every subsequent skill can reference it without re-reading the codebase; can emit a self-contained HTML companion report under analysis/.