菜单
Run a comprehensive pre-PR validation sweep for the Rexio flight controller. Checks HAL discipline, topic sync, test coverage, CHANGELOG, build system integrity, and code conventions. Use before creating a PR, or when the user says /preflight-check.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Add or modify a topic in the Rexio topic bus. Ensures the enum, struct, metadata table, architecture docs, and tests stay in sync. Use when modifying topic_data.h, adding topic publish/subscribe calls, or when the user says /add-topic.
Scaffold a new Rexio ESP32-S3 flight controller component with all required files, tests, mocks, and build system wiring. Use when creating a new component in components/rexio_* or when the user says /new-component.
Guide a strict test-driven development cycle for a Rexio component. Enforces RED-GREEN-REFACTOR: write failing test first, then implement minimum code to pass, then refactor. Use when implementing component logic, or when the user says /tdd-cycle.
Create or modify a FreeRTOS task in the Rexio flight controller. Handles task creation, core pinning, priority, stack sizing, topic pub/sub wiring, and watchdog registration. Use when adding a new RTOS task or modifying task architecture, or when the user says /wire-task.
| name | preflight-check |
| description | Run a comprehensive pre-PR validation sweep for the Rexio flight controller. Checks HAL discipline, topic sync, test coverage, CHANGELOG, build system integrity, and code conventions. Use before creating a PR, or when the user says /preflight-check. |
Run a comprehensive validation of the current branch before PR creation. Report ALL findings — do NOT fix them. The user decides what to act on.
Run make lint and make test (in that order). Both must pass. If either fails, report the failure and continue with remaining checks — do not stop.
Grep all .c files under components/ for direct ESP-IDF hardware calls that should go through the HAL vtable instead. Run the check script if it exists:
bash .claude/skills/preflight-check/scripts/check_hal_discipline.sh
If the script doesn't exist, manually grep for these patterns in components/ source files (excluding components/rexio_hal/src/hal_*_esp.c which ARE the HAL implementations):
esp_timer_get_time — should use g_hal_time->get_time_us()gpio_set_level / gpio_get_level — should use g_hal_gpio->set_level() / get_level()i2c_master_ — should use g_hal_i2c->write_read() / write()rmt_transmit / rmt_receive — should use g_hal_rmt->transmit() / receive()vTaskDelay inside component logic (acceptable in task functions, not in component libraries)esp_rom_delay_us — should use g_hal_time->delay_us()Exceptions: code guarded by #if !defined(REXIO_HOST) or #ifdef REXIO_TARGET is acceptable in HAL implementation files only.
Report: list each violation with file:line.
Grep these flight-critical component directories for heap calls:
components/rexio_controller/components/rexio_mixer/components/rexio_estimator/components/rexio_ahrs/components/rexio_topics/components/rexio_commander/Search for: malloc, calloc, realloc, free, strdup, asprintf, new (C++ leak).
Exceptions: none. These components must be statically allocated.
Report: list each violation with file:line.
Verify that every topic in the enum has all required artifacts. Run the check script if it exists:
bash .claude/skills/preflight-check/scripts/check_topic_sync.sh
If the script doesn't exist, manually check:
components/rexio_topics/include/topic_data.hTOPIC_* entry from the topic_id_t enum (before TOPIC_COUNT)typedef struct { ... } topic_{name_lower}_t; exists in topic_data.h
b. A [TOPIC_{NAME}] = sizeof(topic_{name_lower}_t) entry exists in topics.c metadata table
c. A row exists in docs/architecture.md section 5.3 Topic Registry tableTOPIC_COUNT equals the number of enum entriesReport: list any missing artifacts per topic.
For each .c file in components/*/src/:
test/test_{component}.c existsRUN_TEST(test_{component}_ entry exists in test/test_main.cReport: list any components missing tests or test runner wiring.
Check if CHANGELOG.md has been modified in the current branch compared to main:
git diff --name-only main...HEAD | grep CHANGELOG.md
If not modified, emit a WARNING (not a failure — some infrastructure PRs may legitimately skip this).
For each .c file in components/*/src/:
CMakeLists.txt SRCS listtest/CMakeLists.txt source list (for host build)Report: list any source files missing from either build system.
Read all topic struct definitions in topic_data.h. For each float field, verify it has either:
_m, _rad, _pa, _us, _v, _a, _pct, _hz)q[4], motor[4], temperature, mag_x/y/z)Report: list any fields with unclear units.
Print a summary table:
PREFLIGHT CHECK RESULTS
═══════════════════════
[PASS/FAIL] Build verification (lint + test)
[PASS/FAIL] HAL discipline (N violations)
[PASS/FAIL] No malloc in flight path (N violations)
[PASS/FAIL] Topic contract sync (N missing artifacts)
[PASS/FAIL] Test coverage (N components missing tests)
[PASS/WARN] CHANGELOG updated
[PASS/FAIL] CMakeLists.txt sync (N missing entries)
[PASS/WARN] Unit conventions (N unclear fields)
Overall: N passed, N failed, N warnings
Then list details for any non-PASS items.
make build (ESP-IDF build) — only host lint + test.