ros2-patterns_skill

Overview

This skill provides ROS 2 node templates and common message type patterns for building reliable robotics software. It accelerates development by offering publisher, subscriber, service, and action scaffolds that follow ROS 2 Humble conventions. The content emphasizes error handling, documentation, and extendable Python examples.

How this skill works

The skill supplies ready-to-use Python templates for common ROS 2 patterns: publishers, subscribers, service servers, and action servers. It outlines node structure, initialization, spinning, and clean shutdown, and points to message type guidance for selecting appropriate ROS messages. Developers copy a template, adapt callbacks and topics, and add error handling and docstrings to match their application.

When to use it

• Starting a new ROS 2 node or package
• Implementing publisher/subscriber communication quickly
• Adding request/response behavior with service servers
• Creating long-running tasks with action servers
• Learning ROS 2 Humble node lifecycle and conventions

Best practices

• Begin from the provided templates to ensure consistent structure and naming
• Follow ROS 2 Humble conventions for node names, QoS, and topic design
• Always add try/except blocks around I/O or hardware access and log meaningful errors
• Include clear docstrings and inline comments for callbacks and message flows
• Use appropriate QoS settings for reliability and latency requirements
• Destroy nodes and call rclpy.shutdown() to ensure graceful termination

Example use cases

• A sensor node publishing range or IMU data at a fixed rate using the publisher template
• A perception component subscribing to sensor topics and publishing detected objects
• A control interface exposing commands via a service server for single-shot requests
• A motion planner running as an action server to manage goal preemption and feedback
• Educational examples demonstrating message type choices and callback patterns