new-workspace
Bootstrap a complete ROS 2 colcon workspace from scratch — dir layout, .gitignore, README, this .claude/ config, and seed interfaces/core/bringup packages.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/harunkurtdev/ros2-claude-code-template/HEAD/.claude/commands/new-workspace.md -o ~/.claude/commands/new-workspace.mdnew-workspace.md
Create a brand-new, ready-to-build ROS 2 workspace.
Argument handling (`$ARGUMENTS`):
1. `<workspace_path>` — where to create it (e.g. `~/my_robot_ws`)
(required).
2. `[project_prefix]` — package name prefix (e.g. `acme`). If missing,
derive from the workspace folder name or ask.
If anything is unclear (path already exists, prefix), ask before acting.
Process:
1. Read the `new_ros2_workspace` skill end to end.
2. Verify `<workspace_path>` does not already contain a `src/`.
3. Create the layout: `<ws>/src`, `.gitignore` (build/ install/ log/),
top-level `README.md` with the build/source/test commands; `git init`
(ask first).
4. Copy this template's `.claude/` into the new workspace root so the
slash commands work there (skip if creating inside the template repo).
5. Seed packages in dependency order, delegating to the
`new_ros2_package` skill / `/new-package`:
* `<prefix>_interfaces` (ament_cmake) — only if custom msgs are needed.
* `<prefix>_core` (Clean Architecture, language per user).
* `<prefix>_bringup` (ament_python) — top-level launch/config.
6. Print:
* the tree that was created,
* `cd <ws> && colcon build --symlink-install && source install/setup.bash`,
* the follow-up commands for the project's domain
(`/new-vda5050-connector`, `/new-controller`, `/new-bt-node`, …).
Do **not** run `colcon build` automatically — let the user review first.
Confirm workspace name/path and project prefix before scaffolding.Use proactively before opening a PR that adds or changes BehaviorTree.CPP nodes or BehaviorTree.ROS2 wrappers (RosActionNode/RosServiceNode/RosTopicPub/SubNode, TreeExecutionServer). Reviews a diff against BT.CPP v4 conventions — node base-class choice, non-blocking ticks, ports/blackboard typing, factory/plugin registration, XML v4, and the ROS 2 wrapper contract. Returns a punch list with file:line anchors, not a rewrite.
Use when a design decision touches Clean Architecture boundaries in a ROS 2 project — which layer a new behaviour belongs to, whether a port belongs in domain or application, whether a new node should be lifecycle-managed, whether to compose nodes or split packages. Returns an architectural recommendation with trade-offs, not implementation.
Use when a design decision touches the gz-sim ECS — where new state should live, which system phase should write it, how to avoid coupling, whether to add a component vs. a member variable, whether a new system should be split or merged with an existing one. Returns an architectural recommendation with trade-offs, not implementation.
Use proactively before opening any gz-sim PR. Reviews a diff against the project's C++17 style, ECS conventions, plugin registration patterns, CMake structure, test placement, Migration.md / Changelog.md expectations, and pre-commit configuration. Returns a punch list, not a rewrite.
Use proactively before opening a PR that adds or changes a ros2_control controller, broadcaster, or hardware component (incl. URDF <ros2_control> bringup). Reviews a diff against ros2_controllers / ros2_control_demos conventions — controller & hardware lifecycle, command/state interface configuration, real-time safety of update()/read()/write(), generate_parameter_library usage, pluginlib registration, chainable-controller correctness, URDF wiring, and tests. Returns a punch list with file:line anchors, not a rewrite.
Use proactively before opening any ROS 2 / Nav 2 PR. Reviews a diff against this template's Clean Architecture, ROS 2 communication, lifecycle, testing, and Nav 2 plugin conventions. Returns a punch list with file:line anchors, not a rewrite.
Use proactively before opening a PR that touches a VDA 5050 connector / fleet bridge. Reviews a diff against VDA 5050 v3.0.0 protocol compliance (topics, QoS, header rules, base/horizon, action state machine, schema validation) and the template's Clean Architecture for the MQTT↔Nav 2 bridge. Returns a punch list with file:line anchors, not a rewrite.
Build the colcon workspace (optionally a single package) and report the outcome.