esp32-pin-audit
Audits GPIO assignments in ESP32-family firmware against the verified pin facts of the actual target chip and board, flagging flash/PSRAM pins, strapping pins, input-only pins, USB-Serial-JTAG and UART0 console pins, JTAG pins, ADC2/Wi-Fi conflicts, double assignments and pin-map drift. Use when the user asks "which pins can I use", "is GPIO 12 safe", "check my pinout", "pin conflict", "strapping pin", "board won't boot after wiring", "can't flash after connecting a sensor", "ADC2 with Wi-Fi", "input-only pin", "/pin-audit", or before adding any GPIO, I2C, SPI, UART, ADC or LEDC code on ESP32, ESP32-S2, ESP32-S3, ESP32-C2, ESP32-C3, ESP32-C5, ESP32-C6, ESP32-H2 or ESP32-P4.
- Version
- 0.2.0
- License
- MIT
Pinned to revision f4b67c33f6fb, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/esp32-pin-audit/SKILL.md
- skills/esp32-pin-audit/agents/openai.yaml
- skills/esp32-pin-audit/references/boards/README.md
- skills/esp32-pin-audit/references/boards/esp32_devkit_v1.md
- skills/esp32-pin-audit/references/boards/m5stack_stickc_plus2.md
- skills/esp32-pin-audit/references/boards/m5stack_sticks3.md
- skills/esp32-pin-audit/references/hardware_limitations.md
Every link opens the file at its source, pinned to the revision this page describes.