Menu
Use when reviewing rt-claw changes for OSAL boundary violations, RTOS coupling, platform leakage, driver layering, or portability risks.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when adding CI coverage for a new rt-claw module, feature chain, endpoint backend, service integration, or regression.
Use when building rt-claw, choosing a platform target, running QEMU, flashing hardware, or debugging C/Meson/native build failures.
Use when finding rt-claw definitions, call sites, subsystem ownership, build wiring, OSAL boundaries, or platform-specific implementations.
Use when analyzing rt-claw build logs, QEMU output, serial monitor logs, CI failures, network/API failures, or boot/runtime crashes.
Use when rt-claw behavior, APIs, configuration, build commands, platforms, or developer workflows change and documentation may need synchronization.
Use when adding a new rt-claw service, driver, tool, platform helper, platform port, or RTOS backend.
| name | rt-claw-osal-review |
| description | Use when reviewing rt-claw changes for OSAL boundary violations, RTOS coupling, platform leakage, driver layering, or portability risks. |
| license | MIT |
Review layering before style. The most important rule is that code in claw/
uses project abstractions and does not bind directly to an RTOS or vendor SDK.
claw/ should include claw_os.h and project headers, not RTOS/vendor
headers.osal/<rtos>/.platform/ or hardware drivers.claw/osal/<rtos>/platform/<board>/platform/common/<vendor>/drivers/<subsystem>/<vendor>/CLAW_<SUBSYSTEM>_<PARAM>Lead with findings ordered by severity. Include file and line references when available. If no issues are found, say that clearly and mention remaining validation gaps.
claw/.