القائمة
Use when: updating base node deployment, meshsa-base systemd service, Raspberry Pi 5 setup, mesh-up.sh, FreeTAKServer bridge install, env files, field runbooks, or ops scripts.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when: working in packages/jetson_yolo_gcs — adding a detector backend (YOLO/Hailo/ONNX/TensorRT), a tracker backend (Norfair/SORT), GStreamer camera/egress pipeline, the MAVLink LANDING_TARGET bridge, precision-landing safety, or the perception pipeline failure policy.
Use when: running pre-PR checks, performing regression testing, validating ruff linting/formatting, verifying mypy type safety, and checking test coverage before pushing.
Use when: working on the optional NVIDIA Nemotron inference bridge — meshsa.inference, NemotronClient/InferenceService/NemotronConfig, MESHSA_INFERENCE_* env vars, aiohttp session reuse, [AI Insight] feedback-loop filter, or the aioresponses test mocks.
Use when: adding or changing metrics/health export — RouterMetrics, render_prometheus, per-transport counters, the /metrics or /healthz route, HealthConfig fields, or a Grafana golden-signal dashboard.
Use when: touching the supervised two-way command path (Initiative C) — meshsa.command.*, flightctl/run_commander.py, arm/disarm/RTL/set_mode, COMMAND_INT/ACK, force-disarm, operator confirmation, command audit log, or arm preconditions.
Use when: starting a roadmap/initiative feature, new milestone work, a transport/codec/backend that adds behavior, or any change big enough to need a design. Author or update a spec under docs/specs first; code cites the spec by section.
| name | ops-deploy-base-node |
| description | Use when: updating base node deployment, meshsa-base systemd service, Raspberry Pi 5 setup, mesh-up.sh, FreeTAKServer bridge install, env files, field runbooks, or ops scripts. |
| argument-hint | Target node type, deployment path, service change, and validation available |
ops/base-service install docs, env examples, or systemd unit.ops/pi5-node provisioning scripts or mesh setup.meshsa-base as the installed entry point; do not reference deleted root
scripts or old meshsa_framework paths..env.example files.KillSignal=SIGINT) for the asyncio bridge.ops/base-service/INSTALL_base_node.mdops/base-service/base.env.exampleops/base-service/meshsa-base.serviceops/pi5-node/README_pi5_node.mdops/pi5-node/mesh-up.shops/pi5-node/setup_pi5_node.sh