integrate-module-into-layer

Integrate ROS 2 modules into layer bringup packages with topic remapping.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires launch, roscore, node, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of integrating a ROS 2 module into the appropriate layer's bringup package in the autonomy stack, ensuring the module launches automatically and handles topic remapping and namespace configuration.

Core Features & Use Cases

  • Layer-Specific Integration: Integrates a module into the correct layer's bringup package, e.g., interface, sensors, perception, etc.
  • Topic Remapping: Automates topic name translation for proper inter-module communication.
  • Namespace Configuration: Ensures nodes operate in the correct namespace.
  • Use Case: Use this Skill after creating a ROS 2 package to add it to the autonomy stack launch flow, enabling automated and streamlined deployment.

Quick Start

Use the 'integrate-module-into-layer' skill to integrate the module 'new_planner' into the 'local' layer bringup package.

Frequently Asked Questions about integrate-module-into-layer

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

FAQPage Schema
How do I integrate a ROS 2 module into an autonomy stack bringup package?

You can integrate a ROS 2 module into an autonomy stack by automating its addition to the appropriate layer's bringup package, which ensures the module launches automatically and handles topic remapping and namespace configuration.

What does topic remapping do when integrating ROS 2 modules?

Topic remapping automates topic name translation to ensure proper inter-module communication within the autonomy stack. It maps output topics to expected input topics so ROS 2 nodes exchange messages correctly.

Do I need a ROS 2 environment to configure layer-specific module bringup?

Yes, configuring layer-specific module bringup requires a ROS 2 environment and related dependencies like launch, roscore, and node. These are necessary to automate integration and manage namespace configuration.

When do I need to update package dependencies for ROS 2 module integration?

You need to update package dependencies for ROS 2 module integration when adding a newly created package to the autonomy stack launch flow. This ensures the layer-specific bringup package recognizes and properly launches the module.

How do I configure namespaces for ROS 2 nodes in an autonomy stack?

Namespace configuration for ROS 2 nodes is handled automatically during module integration into the autonomy stack. This ensures nodes operate in the correct namespace within their designated layer, such as interface, sensors, or perception.