gdb-start
Start GDB for Vela/NuttX crash dump analysis, coredump debugging, or live target debugging. Supports coredump (*.core), crashlog (*.log), and memory dump (*.bin) files. Uses tmux for GDB process management and gdbmcp MCP server for AI-controlled debugging via gdbrpc socket. Use when: crash analysis, coredump, crashlog, memory dump, GDB debugging, KASAN, assert failure, hardfault, panic, nxstub, online debugging.
vela-build
Build Vela RTOS (NuttX-based) with automatic detection of NuttX and Vela-specific targets. Supports CMake+Ninja, Makefile, and Vela envsetup build system (lunch + m).
vela-run
Run NuttX and Vela RTOS targets on QEMU, FVP, goldfish emulator, and simulator. Supports ARM Cortex-M (MPS3-AN547), ARMv7-A, ARMv8-A, ARMv8-R FVP, goldfish (Android emulator), and native simulator with automatic detection and GDB debugging.
gerritcomment
Fetch and post Gerrit review comments (as JSON) for a given change URL, change number, or Change-Id. Use when you need real review feedback for code fixes or want to post automated review comments.
tmux
Remote control tmux sessions for interactive CLIs (python, gdb, etc.) by sending keystrokes and scraping pane output.
device-4b
Operate Device 4B hardware including firmware download, flashing via fastboot, adb control, serial monitoring via minicom, and JLink debugging. Use when working with Device 4B or 4b device. Integrates with jira-crash for firmware retrieval and gdb-start for debugging.
executor
Manage persistent interactive CLI processes (REPLs, debuggers, database CLIs, NuttX simulator, QEMU). Use when process maintains state across commands. NOT for one-off commands - use Bash. Prefer over tmux for programmatic I/O without terminal emulation.
jira-crash
Fetch crash information from Jira issues, get crash file URLs via crash detail API, download ELF/coredump/log files, and organize files for GDB debugging. Supports multiple cores (ap, cp, sensor, audio) and auto-detects latest crash from tool comments.
git-commit
Commit changes with NuttX checkpatch.sh validation, automatic sign-off, component-based message format, and JIRA linking. Use when the user asks to create a git commit (for example: commit, git commit, commit diff, commit current, commit changes, submit code, submit changes, /commit, /git-commit).
crash-analysis
Systematic NuttX/Vela crash analysis using GDB. Locates crash threads, examines call stacks, inspects memory, and identifies root causes. Requires gdb-start skill for GDB session setup. Use after loading coredump to understand why a program crashed.
kconfig-tweak
Modify Linux kernel or NuttX .config files from command line without interactive menuconfig. Use when needing to enable/disable config options, set values, query option states, or batch-modify kernel configurations in scripts or CI/CD pipelines.
spec-driver
SPEC-Driven Development workflow for transforming ideas into implementations through Requirements → Design → Tasks phases. Inspired by Kiro IDE's spec-driven approach. Use when: (1) starting a new feature with 'help me with requirements', 'design this', 'spec', 'design', 'requirements', (2) creating technical specifications, (3) breaking down features into tasks, (4) reviewing or updating existing specs. Triggers: requirements analysis, technical design, task breakdown, spec workflow, feature design, I want to build.