| name | ros-graph-inspector |
| description | Inspect ROS 2 nodes, topics, services, actions, parameters, and live graph structure to explain what is running and how it is connected. Use when observing or validating a live ROS system. |
ROS Graph Inspector
Overview
Inspect ROS 2 nodes, topics, services, actions, parameters, and live graph structure to explain what is running and how it is connected.
Core Workflow
- Survey the relevant files, configs, runtime signals, or artifacts to identify the important components and boundaries.
- Map the relationships, dependencies, or graph structure that explain how the system or corpus fits together.
- Highlight missing links, risky assumptions, or ambiguous edges that affect understanding or change safety.
- Return a concise map plus the next best checks or follow-up actions.
Deliver
- A structured map of components, dependencies, or graph relationships.
- The highest-risk gaps, missing links, or ambiguous edges.
- Concrete next checks or actions based on the mapped structure.
Guardrails
- Do not infer strong relationships without evidence from code, config, or runtime artifacts.
- Separate confirmed connections from plausible but unverified ones.
- Prefer a smaller high-confidence map over a speculative complete one.
- Avoid commands that actuate hardware, move robots, or change live controller state unless explicitly requested.