launch-files

Create ROS 2 Python launch files with LaunchDescription configurations.

18|2|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/wimblerobotics/ros2-copilot-skills --skill launch-files
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: launch-files
Source: https://github.com/wimblerobotics/ros2-copilot-skills/tree/main/launch-files
Command: npx skills add https://github.com/wimblerobotics/ros2-copilot-skills --skill launch-files

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation of ROS 2 Python launch files to orchestrate nodes and parameters, reducing manual boilerplate.

Core Features & Use Cases

  • Generate LaunchDescription-based configurations using standard ROS 2 APIs (launch, launch_ros), including Node, IncludeLaunchDescription, GroupAction, and SetParameter.
  • Compose complex startup workflows across multiple packages and namespaces for Jazzy and Rolling ROS 2 deployments.
  • Apply best practices for parameter passing, environment setup, and namespace scoping in launch files.

Quick Start

Create a simple LaunchDescription for a package's node named my_node with a parameter file and namespace.

Frequently Asked Questions about launch-files

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

FAQPage Schema
How do I create ROS 2 Python launch files to orchestrate multiple nodes?

To create ROS 2 Python launch files, you build a LaunchDescription object using standard launch and launch_ros APIs to define Node actions and parameterize node startup across packages.

What is the best way to manage namespaces and parameters in ROS 2 launch configurations?

Managing namespaces and parameters in ROS 2 launch configurations involves using GroupAction to scope nodes and passing parameter files directly to Node actions for robust environment setup.

How do I include other launch files in a ROS 2 Python launch file?

To include other launch files in a ROS 2 Python launch file, use the IncludeLaunchDescription action within your LaunchDescription to compose complex startup workflows across multiple packages.

Does this launch file generation approach support both ROS 2 Jazzy and Rolling distributions?

Yes, this launch file generation approach explicitly supports ROS 2 Jazzy and Rolling distributions, applying standard Python launch APIs and best practices for node configuration and argument handling.

Why use Python launch files instead of XML for ROS 2 node startup orchestration?

Using Python launch files for ROS 2 node startup orchestration enables advanced argument handling, dynamic parameter passing, and complex GroupAction structuring that XML formats struggle to support cleanly.

Can I set environment variables and pass arguments across multiple ROS 2 packages in one launch file?

Yes, you can set environment variables and pass arguments across multiple ROS 2 packages within a single Python launch file by structuring your LaunchDescription with proper argument handling and environment setup.