/safe-mode

description: Prevent destructive operations — cautious (warn), lockdown (restrict edits), or clear
argument-hint: <cautious | lockdown <path> | clear>

/safe-mode - Destructive Operation Protection

Guard against accidental damage during AI coding sessions.

Usage

Cautious Mode

/safe-mode cautious

Intercepts Bash commands and warns before destructive operations:

• `rm -rf`, `DROP TABLE`, `TRUNCATE`
• `git push --force`, `git reset --hard`, `git clean -f`
• `chmod 777`, `curl|sh`

Asks you before the command runs, even in auto mode. You decide whether to proceed.

Lockdown Mode

/safe-mode lockdown src/api/

Restricts Edit/Write operations to the specified directory. Blocks changes to files outside the path.

Keyed to the project. Prevents accidental edits to unrelated code during focused work. Lift it with `/safe-mode clear`.

Both Together

/safe-mode cautious
/safe-mode lockdown src/api/

Bash warnings + directory restriction simultaneously.

Clear All

/safe-mode clear

Removes all restrictions for the current session.

Status Check

Report current safe-mode state:

SAFE MODE STATUS
  Cautious: ACTIVE (warns on destructive Bash commands)
  Lockdown: ACTIVE (restricted to src/api/)

Or:

SAFE MODE STATUS
  No restrictions active.

When to Use

| Situation | Command | |-----------|---------| | Production-adjacent code | `/safe-mode cautious` | | Focused refactoring | `/safe-mode lockdown <path>` | | Unfamiliar codebase | `/safe-mode cautious` | | Done with restrictions | `/safe-mode clear` |

---

**Trigger:** Use when starting risky work, refactoring a specific module, or wanting guardrails on AI operations.