debug-module

Diagnoses and resolves issues in ROS 2 modules.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/cindy-woo/cindy-airstack --skill debug-module-cindy-woo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug-module
Source: https://github.com/cindy-woo/cindy-airstack/tree/main/.agents/skills/debug-module
Command: npx skills add https://github.com/cindy-woo/cindy-airstack --skill debug-module-cindy-woo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill systematically diagnoses and fixes issues in ROS 2 modules, addressing common issues like node status, topic connections, data flow, parameter checking, and performance profiling.

Core Features & Use Cases

  • Autonomous Debugging: Provides step-by-step instructions to diagnose and fix issues in ROS 2 modules.
  • Systematic Approach: Guides through diagnostic steps methodically, ensuring thorough problem-solving.
  • Use Case: When your ROS 2 module stops working as expected, this Skill helps you identify the root cause and fix the issue efficiently.

Quick Start

Use the debug-module skill to check if your ROS 2 node is running by running the command: docker exec airstack-robot-desktop-1 bash -c "ros2 node list".

Frequently Asked Questions about debug-module

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

FAQPage Schema
How do I debug a ROS 2 node that stops working as expected?

To debug a ROS 2 node that stops working, this skill provides a systematic approach to diagnose root causes by checking node status, topic connections, and data flow. It guides you step-by-step to identify and fix the module issue efficiently.

What is the best way to check ROS 2 topic connections and data flow during debugging?

The best way to check ROS 2 topic connections and data flow is using a systematic diagnostic approach. This skill methodically analyzes topic connections and data flow alongside parameter checking and performance profiling to resolve module issues.

Does this systematic debugging approach require specific ROS 2 tools?

Yes, this systematic debugging approach requires ROS 2 and associated diagnostic tools. You need an active ROS 2 environment to check node status, inspect topic connections, validate parameters, and run performance profiling commands.

How do I list running ROS 2 nodes to start diagnosing module issues?

To list running ROS 2 nodes and start diagnosing module issues, execute the command `ros2 node list` within your ROS 2 environment. This verifies if your node is active and initiates the systematic debugging process.

What specific ROS 2 problems does a systematic debugging approach solve?

A systematic debugging approach solves common ROS 2 problems including unexpected node status, broken topic connections, irregular data flow, incorrect parameter configurations, and performance bottlenecks. It addresses these issues methodically to ensure thorough problem resolution.