ptsilivis/autonomousguy
10 skills
$npx skills add ptsilivis/autonomousguySkillInstalls
autosar-bswAUTOSAR 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 autosar-swcAUTOSAR 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 achange-and-impactChange-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 code-reviewSenior 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 ucodebase-analysisFirst-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 requirembedded-debuggingSenior 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 classifiembedded-testingEmbedded 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/Diso26262ISO 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 (misraMISRA 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,requirementsRequirements-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 attribu