Ros2 Dev

Expert guidance for ROS 2 (Jazzy) development in Python (rclpy) and C++ (rclcpp). Use whenever the user works with ROS 2 nodes, topics, services, actions, QoS, parameters, lifecycle nodes, executors, callback groups, launch files, colcon/ament builds, package.xml/setup.py, tf2, URDF/Xacro, DDS (Fast-DDS, Cyclone DDS), or ros2 CLI tools (run, launch, topic, node, service, param, bag, doctor). Also trigger on implicit cues: "my node can't see the topic", "messages aren't arriving", "callback not firing", "QoS mismatch", "transform lookup failed", "colcon build fails", "launch file not working", "which message type for", "how do I make two nodes talk", "robot not moving", "how to test a ROS node". ALSO use for ROS 2 + Gazebo simulation debugging -- whenever the user mentions Gazebo, gz sim, ros_gz_bridge, use_sim_time, /clock, sim-to-real, or reports "the laser scan drifts when the robot turns", "the map gets corrupted", "odom doesn't match", "the robot tips over in Gazebo", "the scan is stuck", or any case where a ROS 2 graph and a physics simulator disagree -- even if they don't say "ROS 2" explicitly.

mkdir -p ~/.claude/skills/ros2-dev
curl -L https://claudskills.com/skills/ros2-dev/SKILL.md \
  -o ~/.claude/skills/ros2-dev/SKILL.md

@misc{ros2-dev-2026,
  author    = {robotics-playground},
  title     = {Ros2 Dev [Claude Code skill]},
  year      = {2026},
  publisher = {ClaudSkills},
  url       = {https://claudskills.com/skills/ros2-dev/}
}