Our review
This skill helps locate implementations of features, modes, commands, and messages in the ArduPilot codebase.
Strengths
- Structured search strategies by target type (flight modes, MAVLink messages, parameters, etc.)
- Leverages built-in Grep and Glob tools for efficient searching
- Covers a wide range of code aspects: modes, messages, subsystems, parameters, scheduled tasks
Limitations
- Specific to the ArduPilot codebase, not applicable to other projects
- Requires some familiarity with ArduPilot's code organization
- May miss very new or non-conventional features
Use when you need to find where a specific feature is implemented in ArduPilot.
Avoid for general code search in other projects.
Security analysis
SafeThe skill only suggests using built-in Read, Grep, and Glob tools to locate code patterns. It does not execute any code, modify files, or access external resources, and it explicitly warns against using shell commands. No destructive or exfiltrating actions are possible.
No concerns found
Examples
Find where the 'Guided' mode is implemented in ArduCopter.Where is the MAVLink message LED_CONTROL handled?Find the implementation of the 'RTL' mode in ArduPlane.name: find-code description: Find where features, modes, commands, or messages are implemented in the ArduPilot codebase. Use when the user asks where something is defined, implemented, or handled. argument-hint: "<feature, mode, command, or message>" allowed-tools: Read, Grep, Glob
Find ArduPilot Code
Find the implementation of $ARGUMENTS in the ArduPilot codebase.
IMPORTANT: Use the built-in Grep and Glob tools, NOT shell grep or find commands.
Search strategies by type
Flight modes
Flight modes are classes in vehicle directories:
Glob: ArduCopter/mode_*.cpp
Glob: ArduPlane/mode_*.cpp
Glob: Rover/mode_*.cpp
Mode classes inherit from Mode and are defined in mode.h:
Grep for: class Mode.*$ARGUMENTS
Mode enum values:
Grep for: $ARGUMENTS in ArduCopter/mode.h or ArduPlane/mode.h
MAVLink message handlers
Incoming messages dispatched in GCS_MAVLINK:
Grep for: case MAVLINK_MSG_ID_$ARGUMENTS
Grep for: handle_message_$ARGUMENTS
Features / subsystems
Library implementations in libraries/:
Grep for: class.*$ARGUMENTS in libraries/**/*.h
Singleton access:
Grep for: AP::$ARGUMENTS
Grep for: $ARGUMENTS::get_singleton
Vehicle-specific features
Check the vehicle's main header and cpp files:
Grep for: $ARGUMENTS in ArduCopter/Copter.h
Grep for: $ARGUMENTS in ArduCopter/*.cpp
Parameters
Parameter definitions (use /find-param for detailed search):
Grep for: @Param:.*$ARGUMENTS
Grep for: AP_GROUPINFO.*"$ARGUMENTS"
Scheduler tasks
Tasks registered in vehicle scheduler:
Grep for: SCHED_TASK.*$ARGUMENTS
Grep for: $ARGUMENTS in ArduCopter/Copter.cpp (scheduler_tasks array)
RC auxiliary functions
Auxiliary switch functions:
Grep for: $ARGUMENTS in libraries/RC_Channel/RC_Channel.h
Grep for: case.*$ARGUMENTS in libraries/RC_Channel/RC_Channel.cpp
Log messages
Log message definitions:
Grep for: $ARGUMENTS in libraries/AP_Logger/LogStructure.h
Grep for: Write_$ARGUMENTS in libraries/**/*.cpp
Build options / feature flags
Compile-time enables:
Grep for: $ARGUMENTS in Tools/scripts/build_options.py
Grep for: #if.*$ARGUMENTS in libraries/**/*.h
Search tips
- Start broad with Grep across the whole repo, then narrow down
- Use Glob to find files by naming convention first, then Read specific files
- Check
.hfiles for declarations,.cppfor implementations - ArduPilot uses
_enabledsuffix for feature guards:AP_FEATURE_ENABLED - Singleton classes: look for
_singletonmember andget_singleton()method - Frontend/backend split: frontend in
AP_Foo.h, backends inAP_Foo_Backend*.h
Next.js App Router Expert
Development
A skill that turns Claude into a Next.js App Router expert.
README Generator
Development
Creates professional and comprehensive README.md files for your projects.
API Documentation Writer
Development
Generates comprehensive API documentation in OpenAPI/Swagger format.