control-camera-regression-review

Stars9

Forks3

UpdatedMarch 15, 2026 at 18:11

Review regression-sensitive LawnBerry Pi manual control and camera paths: RoboHAT USB handoff, watchdog feeding, motor authorization, joystick responsiveness, MJPEG and snapshot fallback, camera ownership, and stream backpressure handling.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Source

acredsfan

acredsfan/lawnberry_pi

View GitHub Repository View Creator Repositories

Download

Related occupationsSOC

Based on SOC occupation classification

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations·SOC 15-1253

SKILL.md

readonly

name	control-camera-regression-review
description	Review regression-sensitive LawnBerry Pi manual control and camera paths: RoboHAT USB handoff, watchdog feeding, motor authorization, joystick responsiveness, MJPEG and snapshot fallback, camera ownership, and stream backpressure handling.
argument-hint	What manual-control or camera change should be reviewed or hardened?
user-invocable	true

Control and Camera Regression Review

What this skill does

This skill provides a conservative review workflow for the two highest-regression surfaces called out in the maintainer handbook: manual control and camera streaming.

Read first

docs/developer-toolkit.md
docs/RELEASE_NOTES.md
backend/src/services/robohat_service.py
backend/src/services/camera_stream_service.py
relevant frontend control/camera views, stores, and services
focused tests for RoboHAT and camera streaming

Review procedure

Identify whether the change touches drive control, USB control handoff, blade-related UI coupling, live stream delivery, snapshots, or operator responsiveness.
Trace the backend path end to end.
- control commands and safety gates
- watchdog heartbeat feeding
- motor authorization and interlock checks
- RoboHAT RC vs USB ownership behavior
- camera backend selection, simulation fallback, and client delivery path
Trace the frontend/operator path.
- rate or debounce behavior
- API and WebSocket interaction
- reconnect or fallback handling
- user-visible fault states
Review tests before refactoring and extend focused coverage instead of relying on happy-path smoke tests.
Validate in simulation-safe mode first.

Non-negotiable checks

control changes fail closed when safety state is uncertain
USB control loss does not get hand-waved away as transient noise
camera changes respect centralized device ownership
fallback behavior is explicit, not accidental
performance or responsiveness claims are backed by actual targeted checks from this session

Completion checks

changed control/camera path was traced across API, services, and UI if applicable
regression tests exist or were updated near the sensitive seam
the summary calls out any remaining hardware-sensitive risk clearly

More from this repository

same repository

sim-hardware-validation

acredsfan/lawnberry_pi

Use for LawnBerry Pi simulation vs real-hardware validation. Covers SIM_MODE selection, .env and config checks, simulation-safe test-first workflow, hardware preflight expectations, and avoiding false claims that local success proves on-device behavior.

2026-06-259

ai-model-quality-pass

acredsfan/lawnberry_pi

Use for improving LawnBerry Pi AI result quality without breaking the existing backend contract. Covers ai_service review, model artifact or rule improvement, conservative evaluation, performance notes, and avoiding premature accelerator-specific churn.

2026-03-159

maintainer-doc-sync

acredsfan/lawnberry_pi

Keep LawnBerry Pi maintainer documentation synchronized with implementation. Use when runtime behavior, supported hardware scope, subsystem maturity, immediate focus, two-week plan, release notes, or callable interfaces have changed and docs must be updated in the same pass.

2026-03-159

maintainer-reentry

acredsfan/lawnberry_pi

Use when returning to LawnBerry Pi after time away, starting substantial maintenance, or needing a fast project re-entry workflow. Covers docs to read first, runtime ports, hardware baseline, simulation vs hardware mode, important files by task, and validation planning.

2026-03-159

maintenance-orchestration

acredsfan/lawnberry_pi

Use when a LawnBerry Pi task spans re-entry, specialist routing, implementation, documentation sync, and validation. Covers choosing the right specialist workflow and sequencing investigation, changes, doc updates, and test planning.

2026-03-159

mission-recovery-pass

acredsfan/lawnberry_pi

Use for LawnBerry Pi mission persistence and recovery work. Covers what mission state should survive restart, safe restart semantics, paused vs running recovery behavior, lifecycle validation, and persistence-backed tests.

2026-03-159

name	control-camera-regression-review
description	Review regression-sensitive LawnBerry Pi manual control and camera paths: RoboHAT USB handoff, watchdog feeding, motor authorization, joystick responsiveness, MJPEG and snapshot fallback, camera ownership, and stream backpressure handling.
argument-hint	What manual-control or camera change should be reviewed or hardened?
user-invocable	true

Control and Camera Regression Review

What this skill does

This skill provides a conservative review workflow for the two highest-regression surfaces called out in the maintainer handbook: manual control and camera streaming.

Read first

docs/developer-toolkit.md
docs/RELEASE_NOTES.md
backend/src/services/robohat_service.py
backend/src/services/camera_stream_service.py
relevant frontend control/camera views, stores, and services
focused tests for RoboHAT and camera streaming

Review procedure

Identify whether the change touches drive control, USB control handoff, blade-related UI coupling, live stream delivery, snapshots, or operator responsiveness.
Trace the backend path end to end.
- control commands and safety gates
- watchdog heartbeat feeding
- motor authorization and interlock checks
- RoboHAT RC vs USB ownership behavior
- camera backend selection, simulation fallback, and client delivery path
Trace the frontend/operator path.
- rate or debounce behavior
- API and WebSocket interaction
- reconnect or fallback handling
- user-visible fault states
Review tests before refactoring and extend focused coverage instead of relying on happy-path smoke tests.
Validate in simulation-safe mode first.

Non-negotiable checks

control changes fail closed when safety state is uncertain
USB control loss does not get hand-waved away as transient noise
camera changes respect centralized device ownership
fallback behavior is explicit, not accidental
performance or responsiveness claims are backed by actual targeted checks from this session

Completion checks

changed control/camera path was traced across API, services, and UI if applicable
regression tests exist or were updated near the sensitive seam
the summary calls out any remaining hardware-sensitive risk clearly