Sup Ops

Ops/automation workflow recipe (assess → dry-run → execute → verify → report)

chinkan Updated 11 repo stars

File contents

When to use

When a task asks to run a script, automate a system action, or perform shell-based ops.

Operating rules

  1. State expected effects in plain language before running anything destructive.
  2. Prefer a dry-run or read-only check first when available.
  3. Run inside the configured sandbox directory; never escape it.
  4. Capture command output and exit codes as evidence.
  5. Roll back or document recovery steps for any failure.

Stop conditions

  • The intended system change is verified (state observed, not assumed).
  • All commands and their outputs are recorded.
  • No unintended side effects remain.

chinkan/RustFox commit c8e337ec9f

Frequently asked questions

npx get-skill add chinkan/sup-ops