From rkit
Combined safety mode that orchestrates freeze + destructive detection + automation cap. When active: freezes domain preset, caps automation at L2, enhances Bash scrutiny. Triggers: guard, safety mode, careful mode, 가드, 안전 모드, 조심, ガードモード, 安全モード, 慎重, 守卫模式, 安全模式, 谨慎, modo guardia, modo seguro, mode garde, mode sécurisé, Schutzmodus, Sicherheitsmodus, modalità guardia, modalità sicura Do NOT use for: individual file freeze (use /freeze), automation level control (use /control), PDCA phase management.
npx claudepluginhub solitasroh/rkit --plugin rkitThis skill is limited to using the following tools:
> Combined safety mode: freeze preset + automation L2 cap + enhanced Bash scrutiny.
Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.
Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
Combined safety mode: freeze preset + automation L2 cap + enhanced Bash scrutiny.
| Argument | Description | Example |
|---|---|---|
| (none) | Show guard mode status | /guard |
on [domain] | Activate guard mode | /guard on mcu |
off | Deactivate guard mode | /guard off |
status | Show guard mode status | /guard status |
Guard mode is a single toggle that activates three safety mechanisms simultaneously:
freeze-manager.freezePreset(domain)guard-mode.activate(domain, currentLevel)freeze-manager.unfreezeAll()guard-mode.deactivate().rkit/state/guard-mode.jsonOutput Format:
--- Guard Mode Status ----------------------------
Active : Yes
Domain : mcu
Activated At : 2026-03-25T10:30:00Z
Reason : Guard mode activated for mcu domain
---------------------------------------------------
Freeze Status:
Frozen patterns: 6 (preset: mcu)
*.ld, startup_*.s, *.ioc, system_*.c, ...
Automation Cap:
Current: L2 (capped from L3)
Previous level will restore on /guard off
Domain Rules:
[ON] G-009: MCU Flash programmer detection
[ON] G-010: Kernel/device dangerous operation
[ON] G-011: Certificate/signing operation
---------------------------------------------------
Detects MCU flash programming tools:
openocd, st-flash, STM32_Programmer_CLI, JLinkExe, pyocdDetects kernel/device dangerous operations:
dd if=...of=/dev/, insmod, rmmod, mknod, devmem, echo > /proc/Detects certificate/signing operations:
signtool, certutil -add|-delete|-import, sn.exeGuard mode status is shown in /control status output:
Guard Mode: Active (mcu, L2 cap)
Guard mode auto-applies domain freeze preset. Manual /freeze commands work independently.
Frozen files are checked before every Write/Edit operation (via freeze-manager).
Guard mode enables enhanced Bash scrutiny with domain-specific rules (G-009~G-011).
Auto-suggested when entering Do phase on MCU/MPU/WPF projects:
"Consider activating guard mode with /guard on before implementation."
| File | Purpose |
|---|---|
.rkit/state/guard-mode.json | Guard mode state (active, domain, previousLevel) |
.rkit/state/freeze-list.json | Frozen file patterns (managed by freeze-manager) |
| Module | Function | Usage |
|---|---|---|
lib/control/guard-mode.js | activate(), deactivate(), getStatus() | Guard mode orchestration |
lib/control/freeze-manager.js | freezePreset(), unfreezeAll() | File protection |
lib/control/automation-controller.js | getCurrentLevel(), setLevel() | Automation level control |
lib/control/destructive-detector.js | G-009~G-011 rules | Domain-specific detection |
# Activate guard mode for MCU project
/guard on mcu
# Check guard status
/guard status
# Deactivate and restore previous settings
/guard off
# Activate for MPU (kernel/driver) project
/guard on mpu
# Activate for WPF project
/guard on wpf