ROS 2 engineering skills for coding agents: v1.5.0

Hi everyone, I’m YuJin Hong, a robotics software developer based in South Korea.

I’ve been building ros2-engineering-skills, a collection of guidance, reference docs, and validation tools that coding agents such as Claude Code and Codex can use when working on ROS 2 projects. It installs as a Claude Code plugin with optional hooks, or as a knowledge-only skill for Codex, Cursor, and Gemini CLI, which read the same reference files without the hooks.

I think generating ROS 2 code is quite different from figuring out whether its QoS settings are appropriate, whether lifecycle transitions are handled properly, and what the test results actually let us claim.

This project gives agents material to consult when reviewing those questions. It covers Nav2, TF, lifecycle, QoS, SROS2, deployment, and hardware testing. It’s organized so the agent can find the references relevant to the task without reading every document each time.

I’ve just released v1.5.0. A lot of the work in this version went into checking details against upstream sources and correcting inaccurate guidance, including SROS2 enclaves and certificate rotation, and quaternion and covariance handling. It also adds a small supervisor for running a launch file and handling SIGINT on POSIX.

I also spent time on how verification results should be interpreted. Passing local tests doesn’t necessarily mean something is ready to run on a real robot, and a user approving a test doesn’t mean the technical conditions for running it have been met. At the same time, I wanted to cut down on cases where editing a few lines of documentation turns into an inspection of the entire ROS environment.

This release passed 1,342 Python tests and container integration checks across Humble, Jazzy, Kilted, Lyrical, and Rolling. These checks validate the repository’s tools and examples. I haven’t yet run a controlled comparison of agent work quality with and without the skill.

Installation instructions are in the README, and the changes are listed in the v1.5.0 release notes.

If you use coding agents for ROS 2 work, I’d really appreciate hearing how this behaves in your projects. Please let me know about incorrect explanations, missing topics, or instructions that make the work more cumbersome. Concrete examples of where it helped, or where it pointed the agent in the wrong direction, would be especially helpful!