ros2-debugging

Debug ROS2 systems by verifying TF transforms and inspecting topics.

1|Updated Feb 3, 2026

Search Tags:#debugging #ros2 #robotics #topics #transforms #tf

Ready to run

npx skills add https://github.com/Idate96/codex_skills --skill ros2-debugging

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ros2-debugging
Source: https://github.com/Idate96/codex_skills/tree/main/skills/ros2-debugging
Command: npx skills add https://github.com/Idate96/codex_skills --skill ros2-debugging

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps diagnose and resolve issues within ROS2 systems by providing best practices and commands for checking transforms, topics, and general system health.

Core Features & Use Cases

TF Transform Debugging: Ensures accurate checking of coordinate frame transformations with appropriate timeouts.
Topic Inspection: Provides commands to list, monitor frequency, and echo data from ROS2 topics.
System Diagnostics: Offers tools for checking node status, services, and parameters.
Use Case: When a robot is not moving as expected due to incorrect spatial understanding, use this Skill to debug the TF tree and identify the source of the transform error.

Quick Start

Use the ros2-debugging skill to check the frequency of the /odom topic for 10 seconds.

Frequently Asked Questions about ros2-debugging

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I debug ROS2 transforms when my robot is not moving as expected?▼

Debug ROS2 transforms by checking the TF tree to identify spatial understanding errors. Use this Skill to verify coordinate frame transformations with appropriate timeouts, ensuring accurate data flow for robotic applications that are moving incorrectly.

How do I check the frequency of a ROS2 topic like /odom?▼

Check the frequency of a ROS2 topic by using topic inspection commands to monitor data flow for a specific duration. This Skill provides commands to monitor frequency and echo data from topics like /odom for 10 seconds to diagnose communication issues.

What ROS2 command-line tools do I need to inspect topics and node status?▼

You need understanding of ROS2 command-line tools and concepts like TF buffers and topicHz to inspect topics and node status. This Skill requires these prerequisites to diagnose communication and data flow issues in ROS2 robotic applications effectively.

What is the best way to diagnose communication issues in ROS2 systems?▼

The best way to diagnose ROS2 communication issues is by inspecting topics, checking node status, and verifying services. This Skill provides system diagnostics tools to list, monitor, and echo data from topics to resolve data flow problems in robotic applications.

Why does my ROS2 system have incorrect spatial understanding despite correct topic data?▼

Incorrect spatial understanding in ROS2 often stems from transform errors in the TF tree rather than topic data. Use this Skill to debug TF transforms by checking coordinate frame transformations with appropriate timeouts to locate the source of the error.

What are the limitations of using ROS2 command-line tools for system diagnostics?▼

ROS2 command-line tools for system diagnostics require understanding of concepts like TF buffers and topicHz. This Skill focuses on transform verification and topic inspection, meaning complex internal node logic issues may require additional debugging approaches beyond command-line inspection.