From ros
Manage ROS launch files. Use $ARGUMENTS to specify a package name or launch file path.
How this command is triggered — by the user, by Claude, or both
Slash command
/ros:launchThe summary Claude sees in its command listing — used to decide when to auto-load this command
Manage ROS launch files. Use $ARGUMENTS to specify a package name or launch file path. ## If no arguments provided - list all launch files: ## If package name provided: ### Find package and its launch files: ### Read and parse the launch file: Use the Read tool to read the launch file content, then parse: 1. **Arguments** (`<arg>` tags) - parameters that can be set at launch 2. **Nodes** (`<node>` tags) - what nodes will be started 3. **Parameters** (`<param>` tags) - what parameters are set 4. **Includes** (`<include>` tags) - other launch files included 5. **Remaps** (`<remap>` ...
Manage ROS launch files. Use $ARGUMENTS to specify a package name or launch file path.
echo "=== Launch files in workspace ==="
find ${CATKIN_WS:-catkin_ws}/src -name "*.launch" -type f 2>/dev/null | while read f; do
pkg=$(basename $(dirname $(dirname $f)))
echo "$pkg: $f"
done
echo "=== Installed ROS packages with launch files ==="
for pkg in $(rospack list-names 2>/dev/null | head -20); do
pkg_path=$(rospack find $pkg 2>/dev/null)
if [ -d "$pkg_path/launch" ]; then
echo "$pkg: $pkg_path/launch/"
fi
done | head -15
PKG_PATH=$(rospack find $ARGUMENTS 2>/dev/null)
if [ -n "$PKG_PATH" ]; then
echo "Package: $ARGUMENTS"
echo "Path: $PKG_PATH"
echo ""
echo "Launch files:"
find $PKG_PATH -name "*.launch" -type f 2>/dev/null
else
echo "Package '$ARGUMENTS' not found"
fi
Use the Read tool to read the launch file content, then parse:
<arg> tags) - parameters that can be set at launch<node> tags) - what nodes will be started<param> tags) - what parameters are set<include> tags) - other launch files included<remap> tags) - topic remappingsRead the file directly and parse its contents.
Package: [package_name] File: [launch_file_path]
| Argument | Default | Description |
|---|---|---|
| param1 | default_value | Description of parameter |
| param2 | 100 | Another parameter |
| Node Name | Package | Type | Namespace |
|---|---|---|---|
| your_node | your_package | node_type | / |
| Parameter | Value |
|---|---|
| ~param1 | $(arg param1) |
| ~param2 | $(arg param2) |
# Basic launch
roslaunch [package] [file.launch]
# With arguments
roslaunch [package] [file.launch] arg1:=value1 arg2:=value2
# Example for this launch file:
roslaunch your_package robot.launch param1:=value1 param2:=100
roslaunch --ros-args [package] [file] to see all arguments--screen to see node output in terminalrosnode list after launch to verify nodes startednpx claudepluginhub lopisan/claude-code-plugins --plugin ros/colcon-buildBuilds ROS 2 workspace with colcon and optional args, auto-detects git repo and workspace roots, creates .ros_workspace.txt and colcon_build_options.yaml.
/list-workflowsLists available Looplia workflows from the workflows/ directory by scanning Markdown files, parsing YAML frontmatter, and displaying names, descriptions, steps, and usage examples in a table. Suggests creating one if none found.
/rsiReads .claude/commands/ files plus CLAUDE.md, README.md, ROADMAP.md, PHILOSOPHY.md and others to optimize AI-assisted development process.
/launchGuides users through creating a structured product launch plan with interactive parameter selection for scope, type, phase, and channels.
/launchGenerates platform-specific copy for Product Hunt, Twitter/X, LinkedIn, Hacker News, plus launch checklist, press kit, and timeline.
/launchInitializes persistent oma workflow lifecycle with metadata and state files, runs team-plan then team-prd, starts team-exec if scoped, reports phase and recovery command.