Ros2 Engineering Skills
Agent skill for production-grade ROS 2 development. Progressive-disclosure SKILL.md covering workspace, nodes, executors, QoS, ros2_control, Nav2, MoveIt 2, real-time, and deployment. Works with Claude Code, Codex, Cursor, Gemini CLI.
dbwls99706 · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add dbwls99706/ros2-engineering-skills技能说明
name: ros2-engineering-skills description: > Use for designing, implementing, reviewing, debugging, or validating ROS 2 software and configuration: rclcpp/rclpy nodes, colcon and ament packages, launch files, QoS and DDS, URDF/xacro and tf2, ros2_control, Nav2, MoveIt 2, perception and sensor integration, simulation, SROS2, micro-ROS, multi-robot systems, testing, runtime diagnosis, deployment, and ROS 1 migration. Do not use for general C++ or Python questions unrelated to ROS 2, non-robotics middleware, or web and mobile development. license: Apache-2.0 compatibility: > Knowledge files are platform-neutral. Bundled validators require Python 3.10 or newer; build and runtime verification require the target ROS 2 environment. metadata: author: dbwls99706 version: "1.3.0" repository: "https://github.com/dbwls99706/ros2-engineering-skills"
ROS 2 Engineering Skills
Single responsibility: This skill is an API reference & code template guide for ROS 2 development. It tells you how to use ROS 2 APIs correctly and what mistakes to avoid. It does NOT do CI/CD orchestration, incident response, data analysis, or deployment automation — those are separate skill categories.
A progressive-disclosure skill for ROS 2 development — from first workspace to
production fleet deployment. Detailed patterns and code templates live in
references/; read the relevant file before writing code.
How to use this skill
This always-loaded file carries routing, core principles, pitfalls, and
anti-patterns — enough for quick questions and architectural decisions.
For implementation work, use the Decision Router below to load the
reference file(s) matching the task; the AI pitfalls table lists mistakes
worth re-checking before generating code. scripts/ are tools to run
(scaffolding, QoS checking, launch validation), not reading material.
When domains intersect (e.g. Nav2 + ros2_control) and recommendations
conflict, favor safety > determinism > simplicity.
Execution log (opt-in): When the Stop hook runs (Claude Code only) and
the SKILL_RUNS_LOG environment variable is set, a session summary is
appended to .skill-runs.log. If that file exists in the workspace, read the
last few lines to avoid repeating past mistakes. Without the opt-in — and on
platforms without hooks — the file is never created, so a read-only session
leaves the working tree untouched.
Platform support: SKILL.md and references/ are platform-neutral
knowledge documents. scripts/ can be run manually on any platform whose
environment has Python and the repository dependencies. The hook wiring in
hooks/hooks.json and .skill-runs.log are Claude Code-specific; on other
platforms run the validators manually from the skill root:
SKILL_WORKSPACE=<dir> python3 scripts/skill_stop_hook.py and
python3 scripts/skill_validate_hook.py --file <src> / --command '<cmd>'
(the command string is inspected only, never executed; without those flags
the validate hook expects a Claude Code PreToolUse payload and checks
nothing on its own).
Decision router
| User is doing... | Read |
|---|---|
| Creating a workspace, package, or build config | references/workspace-build.md |
| Writing nodes, executors, callback groups | references/nodes-executors.md |
| Topics, services, actions, custom interfaces, QoS | references/communication.md |
| Lifecycle nodes, component loading, composition | references/lifecycle-components.md |
| Launch files, conditional logic, event handlers | references/launch-system.md |
| tf2, URDF, xacro, robot_state_publisher | references/tf2-urdf.md |
| ros2_control, hardware interfaces, controllers | references/hardware-interface.md |
| Real-time constraints, PREEMPT_RT, memory, jitter | references/realtime.md |
| Nav2, SLAM, costmaps, behavior trees | references/navigation.md |
| MoveIt 2, planning scene, grasp pipelines | references/manipulation.md |
| Camera, LiDAR, PCL, cv_bridge, depth processing | references/perception.md |
| Sensor drivers, clock sync, LiDAR-camera extrinsics | references/sensor-integration.md |
| Unit tests, integration tests, launch_testing, CI | references/testing.md |
| ros2 doctor, tracing, profiling, rosbag2, CLI cheat sheet | references/debugging.md |
| "Which install/config/publisher is actually running?" audits | references/runtime-provenance.md |
| Faults crossing ROS and non-ROS layers (link, bridge, driver) | references/system-diagnostics.md |
| Docker, cross-compile, fleet deployment, OTA | references/deployment.md |
| System bringup, udev rules, boot sequence, watchdogs | references/system-bringup.md |
| Gazebo, Isaac Sim, sim-to-real, use_sim_time | references/simulation.md |
| SROS2, DDS security, certificates, supply chain | references/security.md |
| E-stop, safety chains, command arbitration | references/safety-estop.md |
| micro-ROS, MCU/RTOS, XRCE-DDS, rclc | references/micro-ros.md |
| Multi-robot fleet, Open-RMF, DDS discovery scale | references/multi-robot.md |
| Message types, units, covariance, frame conventions | references/message-types.md |
| ROS 1 migration, ros1_bridge, hybrid operation | references/migration-ros1.md |
Cross-cutting concerns: Security, error handling, and QoS are not isolated to single reference files — use your judgment and apply them whenever the data path crosses a trust boundary, a node owns hardware, or communication reliability matters.
Core engineering principles
These apply to every ROS 2 artifact you produce, regardless of domain.