new-command
Author a new slash command under .claude/commands/<name>.md with valid frontmatter, following the template conventions, and index it in CLAUDE.md + README.md.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/harunkurtdev/ros2-claude-code-template/HEAD/.claude/commands/new-command.md -o ~/.claude/commands/new-command.mdnew-command.md
Add a new `/slash-command` to this `.claude/` config.
Argument handling (`$ARGUMENTS`):
1. `<command_name>` — `kebab-case` (required); becomes the file name and
the `/command` name.
2. `[paired_skill]` — the skill this command drives (most commands read a
skill, then act). If missing, ask.
3. `[description]` — one-line imperative summary.
If anything is unclear, ask before writing.
Process:
1. Read the `extending_claude_config` skill (conventions + templates).
2. Verify `commands/<command_name>.md` does not already exist.
3. Create `commands/<command_name>.md` with:
* frontmatter: `description:` (one-line, imperative),
`argument-hint:` (`"<arg1> <arg2> [optional]"`),
`allowed-tools:` (usually `["Bash","Read","Write","Edit"]`).
* body: a short intro, an **Argument handling (`$ARGUMENTS`)** section,
a "if anything is missing, ask first" line, and a numbered
**Process** that (a) reads the paired skill, (b) does the work, and
(c) prints a summary (files created, the next command to run).
* match the structure of a sibling command (e.g. `new-node.md`,
`new-controller.md`).
4. **Index it**: add a row to the **Slash commands** table in
`.claude/CLAUDE.md`, and to the command list in `.claude/README.md`
under "How to use".
5. Print: file created + the index rows added.
A command should defer the real "how" to a skill and stay an
orchestration recipe. Always update both indexes in the same change.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.