iot-quality

Enforce pre-merge quality gates for ESP32 firmware with static analysis.

25|7|Updated Mar 4, 2019
One-click install
npx skills add https://github.com/smart-swimmingpool/pool-controller --skill iot-quality
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: iot-quality
Source: https://github.com/smart-swimmingpool/pool-controller/tree/main/.opencode/skills/iot-quality
Command: npx skills add https://github.com/smart-swimmingpool/pool-controller --skill iot-quality

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quality assurance for embedded/IoT firmware to detect anti-patterns, ensure static analysis, and enforce production-readiness for ESP32 pool-controller projects.

Core Features & Use Cases

  • Static analysis and anti-pattern detection for embedded code
  • Pre-merge quality gates including compilation, linting, and watchdog checks
  • Code review rules and hardening guidance for 24/7 operation and reliability

Quick Start

Run a pre-merge quality check against your ESP32 firmware to verify it meets the established gates.

Frequently Asked Questions about iot-quality

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

FAQPage Schema
How do I enforce production-readiness for ESP32 IoT firmware in CI?

Pre-merge quality gates for ESP32 firmware catch anti-patterns by enforcing compilation, linting, and watchdog checks across pull requests and builds before any code is merged.

What static analysis checks are needed for 24/7 embedded IoT controllers?

Static analysis for 24/7 embedded IoT controllers must detect anti-patterns, verify watchdog feeding, and check NVS endurance to ensure continuous reliable operation.

Can I use automated code review rules for ESP-IDF compatibility gaps?

Automated code review rules verify ESP-IDF API compatibility by applying static analysis and hardening guidance directly to your embedded firmware project during pull requests.

How do I set up pre-merge quality gates for ESP32 pool-controller firmware?

Set up pre-merge quality gates for ESP32 pool-controller firmware by running automated checks that validate compilation, linting, watchdog feeding, and NVS endurance before code merges.

Why does my ESP32 IoT firmware fail production-readiness checks?

ESP32 IoT firmware fails production-readiness checks when static analysis detects blocking anti-patterns, missing watchdog feeds, or ESP-IDF API compatibility gaps during the build process.