ros

Build the ROS catkin workspace. Optional arguments in $ARGUMENTS:

Run roswtf diagnostics and comprehensive ROS system health analysis

Manage ROS launch files. Use $ARGUMENTS to specify a package name or launch file path.

Discover and select ROS master for this session. Run before other ROS commands.

Manage ROS parameters. The user may provide various subcommands in $ARGUMENTS.

Use this agent when the user has ROS communication problems - topics not connecting, nodes not receiving messages, services timing out, or data flow issues. Trigger examples: - "My node isn't receiving any messages" - "The subscriber doesn't get data from the publisher" - "Topic remapping isn't working" - "Service call times out" - "Messages aren't getting through" - "Why is this topic empty?" - "Debug the connection between node A and B"

Use this agent when the user wants to understand the ROS system architecture, explore node relationships, trace data flow, or get an overview of how the robot system works. Trigger examples: - "Explain how this ROS system works" - "What nodes are running and what do they do?" - "How does sensor data flow through the system?" - "Which node publishes to /sensor/data?" - "Map out the ROS graph" - "Show me the system architecture" - "What topics does node X use?"

Use this agent for continuous background monitoring of ROS system health - tracking topic rates, detecting node failures, and alerting on anomalies. Trigger examples: - "Monitor the sensor topic rate" - "Watch this topic for drops" - "Keep an eye on the system while I test" - "Track node health during operation" - "My sensor data is intermittent, can you monitor it?" - "Alert me if the rate drops below X Hz" - "Monitor for the next 5 minutes"

Use this skill when the user needs help writing, understanding, or modifying ROS launch files. Covers launch XML syntax, arguments, parameters, node configuration, includes, conditionals, namespaces, remapping, and common patterns. Trigger examples: - "How do I create a launch file?" - "Add an argument to this launch file" - "What does $(find pkg) do?" - "How do I include another launch file?" - "Set up conditional launching" - "Configure node parameters in launch"

Use this skill when the user asks about ROS message types, message fields, sensor_msgs, geometry_msgs, std_msgs, nav_msgs, or needs to understand how to work with specific message structures like sensor_msgs/Imu, geometry_msgs/Twist, nav_msgs/Odometry, etc. Trigger examples: - "What fields are in sensor_msgs/Imu?" - "How do I publish a Twist message?" - "What's the difference between Pose and PoseStamped?" - "Show me the Odometry message structure" - "What units does IMU use?"

Use this skill when the user encounters ROS errors, issues, or unexpected behavior. Covers common error messages, diagnostic approaches, and proven solutions for roscore issues, topic problems, build errors, network issues, and more. Trigger examples: - "Unable to communicate with master" - "Topic not found" - "Node crashed" - "Transform error" - "Build failed" - "roswtf shows warnings" - "Message type mismatch"

1 hook across 1 event