What problem does it solve? Changing STM32 pin, peripheral, clock, or initialization settings normally requires manual edits in STM32CubeMX and careful regeneration without losing hand-written code. This Skill automates that workflow through the EmberProbe Agent Bridge, with authorization controls, baseline drift detection, and recovery snapshots. ## Core Features & Use Cases - Candidate-based configuration editing: Generate a candidate .ioc file from JSON property changes or deletions without touching the original project, then preview a categorized diff before applying. - Two-stage authorized regeneration: Prepare and inspect changes first, then execute only after explicit one-time or 24-hour user confirmation, with persisted request IDs for safe retry after network timeouts. - Consistency checking: Run quick manifest-based checks or deep isolated regeneration checks to detect IOC/source drift and stale generated files without mutating the project. - Use Case: You need to change USART2 baud rate to 115200 and regenerate initialization code. The Skill creates a candidate file, shows the diff, asks for your approval, runs CubeMX headlessly, protects your USER CODE blocks, and reports the actual changed files. ## Quick Start Ask the agent to update a peripheral setting in your .ioc configuration and regenerate the STM32 initialization code, then approve the shown changes when prompted.
