gz-lint
The gz-lint command runs pre-commit hooks including clang-format and codespell against changed files in the gz-sim repository, with options to lint only changes from main, all files, or specified files. It optionally runs clang-tidy against the compile database and reports any automatic fixes that require staging, ensuring code quality without bypassing failed hooks.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/harunkurtdev/ros2-claude-code-template/HEAD/.claude/commands/gz-lint.md -o ~/.claude/commands/gz-lint.mdgz-lint.md
Lint changed files in `/home/rdadmin/gz-sim`. 1. If `$ARGUMENTS` is empty, run only over changed-vs-main: `pre-commit run --from-ref origin/main --to-ref HEAD` 2. If `$ARGUMENTS == "--all"`, run everything: `pre-commit run --all-files` 3. Otherwise treat `$ARGUMENTS` as a space-separated file list: `pre-commit run --files $ARGUMENTS` 4. If clang-tidy is wanted (ask the user), run it against the compile database in `build/compile_commands.json`: `clang-tidy -p build $ARGUMENTS` 5. Report any auto-fixes that pre-commit applied — the user needs to stage them. 6. Do **not** add `--no-verify` to anything; if a hook fails, fix the root cause.
Scaffold a Behavior Tree leaf node — plain BehaviorTree.CPP (SyncActionNode / StatefulActionNode / ConditionNode) or a BehaviorTree.ROS2 wrapper (RosActionNode / RosServiceNode / RosTopicPubNode / RosTopicSubNode) — with ports, factory/plugin registration, and XML v4 usage. Trigger when the user asks to write a behavior-tree node (not Nav 2-specific).
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.
Build the colcon workspace (optionally a single package) and report the outcome.
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.
Author a new skill under .claude/skills/<name>/SKILL.md with valid frontmatter, following the template conventions, and index it in CLAUDE.md + README.md.
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.
Author a new asset for this .claude/ template — a rule, skill, slash command, or sub-agent — following the project's conventions and wiring it into the CLAUDE.md / README.md indexes. Trigger when the user wants to add or extend a command, skill, agent, or rule (make the template itself extensible).
Configure and build gz-sim from source using either CMake/Ninja directly or a colcon workspace. Trigger when the user asks to build, recompile, configure, or set up the gz-sim binary tree.