Slash Command

/device-init

From embedded-target

Scaffold the embedded target loop in this project — DEVICE.md plus the harness/, faults/, and repros/ skeletons.

Invocation

How this command is triggered — by the user, by Claude, or both

Slash command

/embedded-target:device-init

Model invocable

No pre-commands

Context Preview

The summary Claude sees in its command listing — used to decide when to auto-load this command

Scaffold the on-device loop for this project from the plugin's templates at `${CLAUDE_PLUGIN_ROOT}/templates/`. For each target below, copy it from the template only if it does not already exist; never overwrite an existing file — report it as skipped instead.

Copy into the project root:
- `DEVICE.md` ← `templates/DEVICE.md`
- `harness/` ← `templates/harness/` (env.sh, build.sh, deploy.sh, run.sh, device-reset.sh, collect-diag.sh, backtrace.sh, loop.sh, and analyze/)
- `faults/` ← `templates/faults/` (dropout.sh, lossy.sh, partition.sh, sweep-dropout.sh)
- `repros/` ← `templates/repros/` (...

Command Content

23 lines · ~372 tokens

Stats

LanguageShell

Parent stars0

MaintenanceGood

Last CommitJun 12, 2026

Actions

View Source View Plugin View on GitHub View README

Stats

Actions

Tags

Scaffold the on-device loop for this project from the plugin's templates at ${CLAUDE_PLUGIN_ROOT}/templates/. For each target below, copy it from the template only if it does not already exist; never overwrite an existing file — report it as skipped instead.

Copy into the project root:

DEVICE.md ← templates/DEVICE.md
harness/ ← templates/harness/ (env.sh, build.sh, deploy.sh, run.sh, device-reset.sh, collect-diag.sh, backtrace.sh, loop.sh, and analyze/)
faults/ ← templates/faults/ (dropout.sh, lossy.sh, partition.sh, sweep-dropout.sh)
repros/ ← templates/repros/ (issue-template.sh, all.sh)

After copying, chmod +x the copied .sh files.

Then tell the user what they must fill in before the loop runs, in this order:

DEVICE.md — access, services, stack pins, the data-plane interface name, safety constraints.
harness/env.sh — DEVICE_SSH and the timeout values.
The # TODO(project) markers in harness/build.sh, deploy.sh, device-reset.sh, collect-diag.sh, backtrace.sh.

Recommend (do not apply silently) adding an allowlist for harness/, faults/, and repros/ commands to the project's .claude/settings.json so the loop runs unattended while raw arbitrary ssh stays gated. Show the user the entries and let them decide.

Report which files were created and which were skipped.