embedded-review

Cross-review embedded firmware diffs with dual models to detect memory safety and RTOS issues.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/ViewWay/openclaw-skills --skill embedded-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: embedded-review
Source: https://github.com/ViewWay/openclaw-skills/tree/main/embedded-review
Command: npx skills add https://github.com/ViewWay/openclaw-skills --skill embedded-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Expertly orchestrates dual-model cross-review for embedded code changes to catch subtle bugs that single-model reviews miss.

Core Features & Use Cases

  • Dual-model cross-review workflow (Claude Code + Codex) to detect memory safety, ISR, RTOS, and hardware-interface issues.
  • Phase-driven review with ACP payloads, context packaging, and unified reporting for embedded firmware diffs.
  • Use cases include critical feature changes, security-sensitive updates, and complex peripheral configurations.

Quick Start

Activate a dual-model embedded firmware diff review with ACP.

Frequently Asked Questions about embedded-review

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

FAQPage Schema
How do I review embedded firmware diffs for memory safety and RTOS pitfalls?

Dual-model cross-review of embedded firmware diffs detects memory safety, ISR hazards, and RTOS pitfalls by orchestrating two models to analyze commits or file changes, outputting a structured report with consensus findings and severity mapping.

Can I use a dual-model code review workflow for bare-metal Cortex-M projects?

Yes, dual-model code review supports both bare-metal and RTOS-based embedded systems across Cortex-M devices and various toolchains, analyzing C/C++ firmware changes from commits, PRs, or file diffs to identify hardware-interface bugs and anti-patterns.

What is dual-model cross-review and how does it detect interrupt hazards?

Dual-model cross-review is a phase-driven workflow where two models independently review embedded firmware diffs using ACP payloads and context packaging, comparing their findings to reach a consensus on interrupt hazards and memory safety issues.

Does this firmware code review work with standard C/C++ toolchains and PR diffs?

Yes, the firmware code review processes PR diffs and commits across various toolchains, targeting C/C++ embedded systems to uncover anti-patterns, peripheral configuration bugs, and RTOS issues through a unified cross-model reporting workflow.

What's the best way to catch hardware-interface bugs in critical peripheral configurations?

Dual-model cross-review provides phase-driven analysis with context packaging for critical feature changes and complex peripheral configurations, generating a cross-model comparison summary to catch hardware-interface bugs that single-model reviews miss.