ros-robotics

What problem does it solve?

ROS development often struggles to identify whether a project uses ROS 1 (catkin), ROS 2 (colcon/ament), or a mixed setup, making migrations risky without a clear, minimal fix path.

Core Features & Use Cases

• Workspace type detection: identify ros1-catkin, ros2-colcon, or mixed by scanning package.xml and CMakeLists.txt.
• Dependency consistency checks: flag missing or redundant declarations across package.xml, CMakeLists.txt, and launch files to ensure install rules and package dependencies line up.
• Guided fixes and quick validation: propose the smallest, verifiable changes and provide commands to validate builds, tests, and runtime behavior in ROS 1/ROS 2 workflows.
• Real-world scenario: when Nav2 activation fails due to TF or dependency misconfig, the skill points to the exact files to fix and how to verify.

Quick Start

Identify your workspace type with the built-in scripts and load the recommended references to apply the smallest verifiable changes.