new_ros2_workspace

Bootstraps a complete ROS 2 colcon workspace with packages, config, and build setup.

Updated Aug 16, 2026
One-click install
npx skills add https://github.com/three1324/yeonjinautomotive --skill new-ros2-workspace-three1324
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: new_ros2_workspace
Source: https://github.com/three1324/yeonjinautomotive/tree/main/.claude/skills/new_ros2_workspace
Command: npx skills add https://github.com/three1324/yeonjinautomotive --skill new-ros2-workspace-three1324

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Starting a ROS 2 project from zero involves repetitive scaffolding: creating the colcon directory layout, writing .gitignore and README files, seeding interface and bringup packages, and wiring in project conventions. This Skill automates that bootstrap so the workspace is ready to build immediately. ## Core Features & Use Cases - Workspace Scaffolding: Creates the standard colcon layout with src/, .gitignore for build/install/log artifacts, and a top-level README with canonical build commands. - Seed Package Creation: Generates an interfaces package (ament_cmake with rosidl_default_generators), a first Clean Architecture package, and a bringup package (ament_python) in dependency order. - Config Propagation: Copies the .claude/ template configuration so slash commands and rules work from the first commit. - Use Case: A robotics engineer starting a new autonomous vehicle project asks for a fresh workspace; the Skill produces a buildable colcon workspace with interfaces, core, and bringup packages following Clean Architecture conventions. ## Quick Start Create a new ROS 2 workspace called acme_ws with the project prefix acme and seed it with interfaces, core, and bringup packages.

Frequently Asked Questions about new_ros2_workspace

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

FAQPage Schema
How do I create a new ROS 2 workspace from scratch?

Create a root directory with a src/ folder, add a .gitignore excluding build/, install/, and log/, then seed packages in dependency order: interfaces first, then the core package, then bringup. Build with colcon build --symlink-install and source install/setup.bash.

What packages should a new ROS 2 project start with?

Start with an interfaces package (ament_cmake with rosidl_default_generators) if custom messages are needed, a core package following Clean Architecture layers, and a bringup package (ament_python) holding launch files and config. Create them in that dependency order.

Should I use ament_cmake or ament_python for a ROS 2 package?

Use ament_cmake for C++ packages and for interface packages that generate messages, services, or actions. Use ament_python for Python packages such as bringup packages that only hold launch files and configuration.

Does this skill run colcon build automatically after scaffolding?

No, it prints the build commands instead of executing them. The user runs colcon build --symlink-install and source install/setup.bash manually when ready.

When should I use this instead of adding a package to an existing workspace?

Use this only when no workspace exists yet. If a colcon workspace is already present, use the package-creation skill or /new-package command to add individual packages instead.