Embedded-Driver-Review — community Embedded-Driver-Review, firmware-copilot-training, community, ide skills

v1.0.0
GitHub

Acerca de este Skill

Perfecto para Agentes de Análisis de Firmware que necesitan capacidades de revisión de código avanzadas para sistemas embebidos Review embedded firmware code with focus on safety, determinism, and correct hardware interaction.

ozmosko ozmosko
[0]
[0]
Updated: 3/11/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 7/11

This page remains useful for teams, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution
Review Score
7/11
Quality Score
47
Canonical Locale
en
Detected Body Locale
en

Perfecto para Agentes de Análisis de Firmware que necesitan capacidades de revisión de código avanzadas para sistemas embebidos Review embedded firmware code with focus on safety, determinism, and correct hardware interaction.

¿Por qué usar esta habilidad?

Habilita a los agentes a detectar problemas de firmware sutiles utilizando un análisis de contenido integral, centrándose en la seguridad, el determinismo y la interacción de hardware correcta, y aprovechando archivos de especificación en formato Markdown

Mejor para

Perfecto para Agentes de Análisis de Firmware que necesitan capacidades de revisión de código avanzadas para sistemas embebidos

↓ Casos de uso accionables for Embedded-Driver-Review

Revisar el código de firmware embebido para seguridad y determinismo
Depurar problemas de interacción de hardware en sistemas embebidos
Validar el código de firmware contra archivos de especificación en docs/specs/*.md

! Seguridad y limitaciones

  • Requiere acceso al código seleccionado actualmente o al archivo actual
  • Necesita archivos abiertos en el editor y archivos de especificación para una revisión óptima
  • Limitado a la revisión del código de firmware con contexto disponible

Why this page is reference-only

  • - Current locale does not satisfy the locale-governance contract.
  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Install Path

Start With Installation And Validation

If this skill is worth continuing with, the next step is to confirm the install command, CLI write path, and environment validation.
Trusted Recheck

Cross-Check Against Trusted Picks

If you are still comparing multiple skills or vendors, go back to the trusted collection before amplifying repository noise.
Workflow

Move To Workflow Collections For Team Rollout

When the goal shifts from a single skill to team workflows, approvals, and repeatable execution, move into workflow collections.
Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is Embedded-Driver-Review?

Perfecto para Agentes de Análisis de Firmware que necesitan capacidades de revisión de código avanzadas para sistemas embebidos Review embedded firmware code with focus on safety, determinism, and correct hardware interaction.

How do I install Embedded-Driver-Review?

Run the command: npx killer-skills add ozmosko/firmware-copilot-training/Embedded-Driver-Review. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for Embedded-Driver-Review?

Key use cases include: Revisar el código de firmware embebido para seguridad y determinismo, Depurar problemas de interacción de hardware en sistemas embebidos, Validar el código de firmware contra archivos de especificación en docs/specs/*.md.

Which IDEs are compatible with Embedded-Driver-Review?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for Embedded-Driver-Review?

Requiere acceso al código seleccionado actualmente o al archivo actual. Necesita archivos abiertos en el editor y archivos de especificación para una revisión óptima. Limitado a la revisión del código de firmware con contexto disponible.

↓ How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add ozmosko/firmware-copilot-training/Embedded-Driver-Review. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use Embedded-Driver-Review immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

Embedded-Driver-Review

Install Embedded-Driver-Review, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

Firmware Code Review

Goal

Review embedded firmware code with focus on safety, determinism, and correct hardware interaction.

The review should help detect subtle firmware issues that may not be visible in standard software code reviews.

Inputs

The review should use the following context when available:

  • the currently selected code or current file
  • any open files in the editor
  • specification files under:

docs/specs/*.md

If a relevant specification exists, use it to validate register usage and device interaction.

If required context is missing, ask for the relevant file.

Review Focus

Perform the review using embedded firmware best practices.

Check for the following categories.

RTOS and Concurrency

  • blocking calls inside ISR context
  • incorrect use of RTOS APIs
  • shared state without synchronization
  • potential race conditions
  • unsafe interrupt interaction

Hardware Register Access

  • incorrect register addresses
  • incorrect bit masks
  • missing bit clearing before setting fields
  • unsafe register modification patterns
  • missing verification reads

Integer and Memory Safety

  • integer overflow
  • narrowing conversions
  • signed / unsigned mismatches
  • unsafe casts
  • implicit type conversions

Error Handling

  • inconsistent error propagation
  • ignored return values
  • missing timeout handling
  • silent failures

Timing and Determinism

  • potential blocking behavior
  • unexpected loops
  • operations that may violate timing constraints

Specification Consistency

If a specification file exists under:

docs/specs/

compare the implementation against the specification.

Check:

  • register usage
  • bitfields
  • initialization sequence
  • configuration values

Report any mismatch between the code and the specification.

Do not assume undocumented behavior.

Output Format

Group findings by severity:

Critical

Issues that may cause:

  • incorrect hardware behavior
  • data corruption
  • system instability

Major

Issues that may cause:

  • incorrect edge-case behavior
  • maintainability problems
  • hidden firmware risks

Minor

Issues related to:

  • readability
  • defensive programming
  • minor safety improvements

Constraints

Do not suggest large architectural refactors.

Prefer minimal fixes that:

  • preserve existing behavior
  • maintain the current API
  • avoid unnecessary complexity

If the issue cannot be evaluated due to missing context, request the relevant files.

Habilidades relacionadas

Looking for an alternative to Embedded-Driver-Review or another community skill for your workflow? Explore these related open-source skills.

Ver todo

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

★ 333.8k
⑂ 0
Inteligencia Artificial

widget-generator

Logo of f
f

Generar complementos de widgets personalizables para el sistema de feeds de prompts.chat

★ 149.6k
⑂ 0
Inteligencia Artificial

flags

Logo of vercel
vercel

El Marco de React

★ 138.4k
⑂ 0
Navegador

pr-review

Logo of pytorch
pytorch

Tensores y redes neuronales dinámicas en Python con fuerte aceleración de GPU

★ 98.6k
⑂ 0
Desarrollador