ros2-patterns

ROS 2 publisher templates provide ready-to-use node scaffolding that handles message creation, topic publishing, and QoS configuration. Use the publisher.py template as a starting point, adapt the message type and topic name for your hardware, and follow the included comments for integration with Humble conventions.

ROS 2 communication patterns serve different needs: publishers and subscribers handle continuous data streams, services enable request-response interactions, and actions support long-running tasks with feedback. This Skill provides templates for all four patterns with documented usage scenarios and standard QoS configurations.

Yes. These templates are specifically designed for ROS 2 Humble development contexts. They include error handling, docstrings, comments, adherence to Humble conventions, and standard QoS configurations built in.

ROS 2 service and action server templates provide node structures with error handling and QoS configuration pre-configured. Adapt the service or action server template to your message types and callback logic, following the documented patterns and Humble conventions included.

The templates include common ROS 2 message type definitions ready for publishers, subscribers, services, and actions. Adapt these predefined types to your specific robotics hardware and use case following the template guidance.