chinkan When to use
When a task asks to run a script, automate a system action, or perform shell-based ops.
Operating rules
- State expected effects in plain language before running anything destructive.
- Prefer a dry-run or read-only check first when available.
- Run inside the configured sandbox directory; never escape it.
- Capture command output and exit codes as evidence.
- 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.