wedsamuel1230/arduino-skills

Overview

This skill provides automated, focused code review for Arduino, ESP32, and RP2040 projects with emphasis on best practices, memory safety, and common embedded pitfalls. It generates actionable, project-specific checklists and concrete suggestions to improve reliability, power usage, and maintainability. Use it to catch issues before publishing, deploying, or final testing.

How this skill works

The tool statically analyzes source files and scans for common embedded code smells: unsafe String usage, blocking delays, buffer and stack risks, hardcoded credentials, and missing error handling. It outputs categorized findings (Critical / Important / Nice to have), a remediation checklist, and specific code suggestions like replacing String with snprintf, using millis() patterns, and verifying sensor initialization. It can analyze single files, directories, or accept pasted code for interactive review.

When to use it

• When you say "review my code" or need an automated check
• Before publishing a sketch or pushing to GitHub
• After adding a feature but before final testing
• When the project "works but feels fragile"
• When preparing for battery-powered or production deployments

Best practices

• Avoid String in time-critical loops; use static char buffers and snprintf
• Replace delay() with millis() non-blocking scheduling for responsiveness
• Declare pin assignments and thresholds in a config header, not magic numbers
• Check and gracefully handle peripheral and network init failures
• Name constants and variables consistently; keep functions small and single-purpose

Example use cases

• Scan a sketch for memory fragmentation and get step-by-step fixes
• Generate a project-specific review checklist before a repo release
• Detect blocking code and refactor loops to use millis() scheduling
• Verify sensor initialization and add visual/serial error feedback
• Find hardcoded credentials and suggest secure config file patterns