nxp-mcu-build-verify

Detect NXP MCU projects and select native build workflows for IAR, Keil, MCUXpresso IDE, and VS Code.

27|5|Updated Mar 28, 2026

Search Tags:#verification #build #windows #mcu #mcuxpresso #keil #iar

Ready to run

npx skills add https://github.com/0xchaihu/nxp-mcu-build-verify --skill nxp-mcu-build-verify

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: nxp-mcu-build-verify
Source: https://github.com/0xchaihu/nxp-mcu-build-verify/tree/main
Command: npx skills add https://github.com/0xchaihu/nxp-mcu-build-verify --skill nxp-mcu-build-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Detects the nearest NXP MCU project and selects the correct native build workflow for Windows environments.

Core Features & Use Cases

Auto-detects the nearest supported NXP MCU project and applies the appropriate native toolchain.
Supports IAR (.ewp), Keil (.uvprojx), MCUXpresso IDE (.project + .cproject), and MCUXpresso VS Code (CMakePresets.json or .code-workspace + .vscode/tasks.json) projects.
Emits compact, machine-friendly output and host_execution_command hints while enforcing non-GCC builds for the listed IDEs.

Quick Start

Run powershell -ExecutionPolicy Bypass -File "<skill-root>\scripts\detect-build.ps1" -ProjectRoot "<path-to-project>" to detect the NXP MCU project type and preview the corresponding host build command.

Frequently Asked Questions about nxp-mcu-build-verify

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

FAQPage Schema

How do I verify an NXP MCU project build on Windows?▼

To verify an NXP MCU build on Windows, run the detection script to auto-identify the nearest project type and preview the native toolchain command. It supports IAR, Keil, and MCUXpresso projects natively.

Does the build verification tool support MCUXpresso VS Code projects?▼

Yes, build verification supports MCUXpresso VS Code projects. The tool detects CMakePresets.json or .code-workspace configurations alongside .vscode/tasks.json to determine the correct workflow.

What NXP MCU project file formats are automatically detected for building?▼

Automatic detection supports IAR .ewp files, Keil .uvprojx files, and MCUXpresso IDE .project with .cproject files. It also identifies MCUXpresso VS Code CMakePresets or workspace files.

Why does my NXP MCU build verification prevent GCC fallback for IDE projects?▼

Build verification prevents GCC fallback for listed IDEs to enforce strict toolchain fidelity and avoid incorrect compilation environments. It mandates non-GCC builds for IAR, Keil, and MCUXpresso projects.

How do I preview a dry-run build command for an IAR or Keil MCU project?▼

Preview a dry-run build command by executing the detection script with your project root path. The script emits a compact, machine-friendly host_execution_command hint without running the actual build.