gz-changelog
The gz-changelog command analyzes commits on the current branch compared to a specified base (defaulting to origin/main) and generates a Changelog.md-formatted summary organized by commit type: Features, Fixes, Documentation, Infrastructure/CI, and Refactor/Cleanup. Use this before releasing to quickly produce changelog entries, identify migration-worthy changes, and decide where to insert the summary in your changelog file.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/harunkurtdev/ros2-claude-code-template/HEAD/.claude/commands/gz-changelog.md -o ~/.claude/commands/gz-changelog.mdgz-changelog.md
Produce a Changelog-friendly summary of the current branch. 1. Determine the base ref: `$ARGUMENTS` if provided, else `origin/main`. 2. Show what's about to be summarised: `git log --oneline <base>..HEAD` 3. For each commit, classify it as one of: * **Features** (new public API or system), * **Fixes** (bug fix referenced by issue/PR), * **Documentation**, * **Infrastructure / CI**, * **Refactor / Cleanup**. 4. Group commits under those headings and produce bullets in the same style as the existing `Changelog.md` (`* Short imperative summary \n * [Pull request #NNNN](...)`). 5. Print the markdown block — do **not** edit `Changelog.md` automatically. Ask whether to insert it under the unreleased / upcoming section. 6. Flag any commits that look like they need a `Migration.md` note (API removals, default changes, plugin renames).
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.