ros-robotics

Detect ROS1 Catkin, ROS2 Colcon, or mixed workspaces and propose minimal fixes.

52|2|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/wzyn20051216/ros-robotics-skill --skill ros-robotics
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ros-robotics
Source: https://github.com/wzyn20051216/ros-robotics-skill/tree/main
Command: npx skills add https://github.com/wzyn20051216/ros-robotics-skill --skill ros-robotics

SYSTEM DOCUMENTATION & REQUIREMENTS

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

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.

Frequently Asked Questions about ros-robotics

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

FAQPage Schema
How do I identify if my ROS workspace is catkin or colcon?

ROS workspace type detection scans package.xml and CMakeLists.txt to identify ros1-catkin, ros2-colcon, or mixed setups. This mechanism checks build system markers and dependency declarations to classify the workspace accurately.

What is the best way to fix Nav2 activation failures caused by TF issues?

Fixing Nav2 activation failures involves flagging missing or redundant declarations across package.xml, CMakeLists.txt, and launch files. The skill points to exact files needing fixes and provides commands to verify TF and runtime behavior.

How do I migrate a ROS1 catkin project to ROS2 ament safely?

Migrating catkin to ament safely requires producing a minimal change plan by analyzing package.xml, CMakeLists.txt, and launch files. This approach proposes the smallest verifiable changes and provides validation commands for builds and tests.

Can I check dependency consistency across ROS2 launch files and CMakeLists?

Dependency consistency checks flag missing or redundant declarations across package.xml, CMakeLists.txt, and launch files. This ensures install rules and package dependencies line up correctly for ROS2 workflows.

Does ros2_control integration require specific package.xml configurations?

ros2_control integration requires consistent dependency declarations across package.xml and CMakeLists.txt. The diagnostic process surfaces minimal verifiable fixes for dependency misconfigurations and validates runtime behavior.