guilyx/dotfiles

commit-and-pr

Create git commits and GitHub/GitLab PRs/MRs using the user's safety protocol. Use when the user asks to commit, open a PR/MR, or push a reviewable branch.

git-flow-hygiene

Apply git flow rules — topic branches, conventional commits, identity, pre-commit gates. Use when preparing branches, commits, MRs/PRs, or before pushing.

ros2-actions

ROS 2 actions — goals, cancel, preemption, feedback, BT integration, and executor pitfalls (Nav2/MoveIt-style). Use when implementing action servers/clients, cancel handshakes, concurrent goals, or stuck RUNNING.

ros2-bag-replay

Record and replay rosbag2 (MCAP), --clock / use_sim_time, remaps, compression, and QoS overrides. Use when bags miss topics, replay has no TF, recording drops, or the user mentions rosbag2, MCAP, bag play, or topic throttle.

ros2-cli-debug

Use ROS 2 CLI to inspect topics, nodes, params, lifecycle, actions, and bags; includes known echo/pub truncation limits for arrays. Use when debugging a live graph, ros2 topic pub/echo quirks, bags, or ros2 doctor output.

ros2-composition

ROS 2 component composition, intra-process communication, UniquePtr callbacks, loaned messages, and Nav2-style container bringup. Use when loading composable nodes, component_container, intra-process, loaned messages, iceoryx, or type adaptation.

ros2-executors

Decide when to use ROS 2 callback groups, MultiThreadedExecutor, mutexes, and async vs sync clients — patterns used by stacks like Nav2 and MoveIt. Use when designing node concurrency, fixing deadlocks, protecting shared state, or when the user mentions…

ros2-interfaces

Author and debug ROS 2 .msg/.srv/.action interfaces — static arrays Type[N], unbounded sequences, IDL/DDS mapping, codegen to C++/Python, and tooling limits (ros2 topic pub/echo, rqt_plot, Simulink). Use when editing message files, interface packages,…

ros2-launch

Write and debug ROS 2 Python launch files — substitutions, OpaqueFunction, composable containers, lifecycle events, namespaces. Use when editing launch.py, IncludeLaunchDescription, LaunchConfiguration, or bringup.

ros2-lifecycle

Author and debug ROS 2 managed (lifecycle) nodes, lifecycle publishers, ordered bringup, and bond-style managers (Nav2-like). Use when implementing configure/activate/deactivate, inactive topics dropping data, or lifecycle managers.

ros2-micro-ros

micro-ROS on MCUs — XRCE-DDS agent, rclc static executors, memory pools, transport (UART/UDP/CAN), and host↔MCU graph limits. Use when embedding ROS 2 on microcontrollers, tuning RMW_UXRCE_* limits, Agent sessions, or when the user mentions micro-ROS, Micro…

ros2-multi-machine

Multi-host / container ROS 2 discovery — multicast vs unicast, Fast DDS Discovery Server, Cyclone peers, ROS_AUTOMATIC_DISCOVERY_RANGE, Docker host network. Use when robots do not see each other, containers isolate DDS, or WAN/multicast is blocked.

ros2-parameters

ROS 2 parameter declare/get, YAML overlays, wildcards, type coercion, and empty-array pitfalls. Use when params are ignored, wrong type, YAML does not load, or the user mentions declare_parameter, allow_undeclared, or empty arrays.

ros2-qos-dds

Diagnose ROS 2 QoS mismatches and DDS discovery issues (RMW, domain ID, localhost-only, Cyclone/FastDDS). Use when topics have 0 subscribers despite running nodes, silent dropouts, multi-machine robots, large images/pointclouds, or the user mentions QoS, DDS,…

ros2-stack-patterns

Portable architecture patterns taken from major ROS 2 stacks (Nav2, MoveIt, ros2_control): composition bringup, lifecycle managers, planner/controller split, action+BT orchestration, realtime loops, planning-scene concurrency. Use when designing or reviewing…

ros2-tf-clock

ROS 2 time, use_sim_time, clocks, and TF2 lookup/extrapolation failures. Use when TF lookup fails, transforms are old, bags replay with wrong time, timers ignore sim time, or the user mentions use_sim_time, tf2, Time, extrapolation, or /clock.

ros2-workspace-ops

Build, test, and source ROS 2 colcon workspaces (ament_cmake/python, rosdep, overlays, parallel-workers). Use for colcon build/test failures, package.xml / CMakeLists issues, workspace setup, or when the user mentions colcon, ament, rosdep, or ROS 2 packages.

session-logging

Write brief Obsidian session logs for agent work. Use at end of meaningful tasks or when the user asks to log what was done.