القائمة
Use when: running pre-PR checks, performing regression testing, validating ruff linting/formatting, verifying mypy type safety, and checking test coverage before pushing.
التثبيت باستخدام 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: 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.
Use when: adding a meshsa codec, changing JSON/Compact/CoT encoding, wire format, codec registry, Envelope serialization, per-transport codec bridge, or decode compatibility.
| name | pre-pr-validator |
| description | Use when: running pre-PR checks, performing regression testing, validating ruff linting/formatting, verifying mypy type safety, and checking test coverage before pushing. |
| argument-hint | Branch diff and verification gates to run |
main.git diff main..HEAD --stat (or git diff main --stat) to see which files have changed.pyproject.toml
with its own ruff/mypy/coverage config; running from the repo root can read the wrong one):
packages/meshsa (enforces 97%+ total coverage, --cov-fail-under=97):
cd packages/meshsa
python -m pytest
ruff check .
ruff format --check .
mypy src
python -m build
packages/jetson_yolo_gcs (enforces 96%+ total coverage, --cov-fail-under=96;
self-contained, must not import meshsa):
cd packages/jetson_yolo_gcs
python -m pytest
ruff check .
ruff format --check .
mypy src
python -m build
select = [E, F, I, UP, B, SIM]) and run
mypy --strict. If the diff also touches jetson_yolo_gcs, confirm no import meshsa was
introduced (grep for it) — that's a hard invariant, not a style preference.geometry/ned.py) stay numpy-free. The sole permitted numpy use is inside the
optional Norfair tracker backend (tracking/norfair_backend.py), where numpy is a lazy,
[tracker]-extra-gated transitive dep of norfair (never declared in dependencies, never
imported at package import — tests/unit/test_imports_clean.py locks both numpy and
norfair out of import jetson_yolo_gcs). Any numpy import outside that backend, or any
numpy added to [project.dependencies], is a regression, not a judgment call. Confirm the
diff introduces no such import and that base import jetson_yolo_gcs stays clean.AGENTS.md (root directory)packages/jetson_yolo_gcs/AGENTS.md (package-local gates + failure policy)docs/NEXTSTEPS.mdpackages/meshsa/pyproject.toml (--cov-fail-under=97)packages/jetson_yolo_gcs/pyproject.toml (--cov-fail-under=96)