Menu
Restart the active YoYoPod dev lane service on Raspberry Pi
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Commit-safe Rust-first dev-lane branch/SHA deploy to Raspberry Pi
Tail YoYoPod runtime/service logs from Raspberry Pi
Manual fallback for fetching CI Rust artifacts onto the Pi (prefer /yoyopod-deploy)
Capture a screenshot of the active YoYoPod display from Raspberry Pi
Health check for Raspberry Pi lanes, runtime, connectivity, processes, memory, recent logs
Sync a committed branch / SHA to the Raspberry Pi dev lane
| name | yoyopod-restart |
| description | Restart the active YoYoPod dev lane service on Raspberry Pi |
| disable-model-invocation | true |
| allowed-tools | ["Read","Bash(yoyopod target:*)"] |
Use deploy/pi-deploy.yaml as the shared deploy contract and
deploy/pi-deploy.local.yaml for machine-specific overrides such as
host, SSH user, dev lane checkout, and branch. yoyopod target restart
is a dev-lane helper and expects the selected checkout to match
/opt/yoyopod-dev/checkout. Prod slot management (target release …)
returns in Round 3 of the CLI rebuild; see
docs/ROADMAP.md.
If the file does not exist yet, run yoyopod target config edit first.
That command creates deploy/pi-deploy.local.yaml automatically before
opening it.
Check lane state first.
yoyopod target mode status
Restart and verify the dev lane service. Run:
yoyopod target restart
Handle failures. If the restart fails because prod is active, use
yoyopod target mode activate dev before retrying. For other
failures, run:
yoyopod target logs --lines 20
Include the relevant error output in your response.
Report whether the dev lane restart succeeded and whether
yoyopod-runtime came up. For prod slot operations, fall back to
direct SSH and systemctl until Round 3 restores the CLI commands.