laurigates/mcu-tinkering-lab

review-firmware

Review embedded C/C++ code changes for best practices

First seen Apr 27, 2026

Installation

$ npx skills add laurigates/mcu-tinkering-lab --skill review-firmware

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from laurigates/mcu-tinkering-lab · top by installs.

npx skills add laurigates/mcu-tinkering-lab

Browse all from laurigates/mcu-tinkering-lab

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 7
License LICENSE
Default branch main
Open issues 38
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Allowed toolsBash(git:*), Read, Grep, Glob

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,460 B
  • docs SUMMARY.md 76 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 13 installs

SKILL.md

Review Firmware Code

Review the firmware code changes: $ARGUMENTS

If no specific files or commit provided, review the most recent changes.

Context

Check recent git changes:

git diff --stat HEAD~1

Review Checklist

Memory Safety

  • Check for buffer overflows and array bounds
  • Verify proper null pointer checks
  • Look for memory leaks (malloc without free)
  • Check stack usage in functions

Resource Management

  • Verify all allocated resources are freed
  • Check for proper GPIO initialization/deinitialization
  • Look for semaphore/mutex deadlock potential
  • Verify interrupt handlers are minimal

ESP-IDF Best Practices

  • Check task stack sizes are appropriate
  • Verify FreeRTOS queue/semaphore usage
  • Look for blocking calls in critical sections
  • Check WiFi/network error handling

Code Quality

  • Verify meaningful variable/function names
  • Check for magic numbers (should be #define or const)
  • Look for duplicated code
  • Verify error codes are properly propagated

Security

  • Check for hardcoded credentials (should be in Kconfig/NVS)
  • Verify input validation
  • Look for unsafe string functions (use snprintf vs sprintf)
  • Check for proper certificate validation

Provide specific line numbers and suggestions for any issues found.