guard · diff
git:20260831.22acaab to git:20261008.79d8ec8
16 added, 10 removed. Audit A to A.
---
name: guard
description: |
Full safety mode: destructive command warnings + directory-scoped edits. Combines /careful (warns before rm -rf, DROP TABLE, force-push, etc.) with /freeze (blocks edits outside a specified directory). Use for maximum safety when touching prod or debugging live systems.
allowed-tools:
- Bash
- Read
- AskUserQuestion
hooks:
PreToolUse:
- matcher: "Bash"
hooks:
- type: command
command: "bash ${CLAUDE_SKILL_DIR:-$HOME/.claude/skills/guard}/../careful/bin/check-careful.sh"
statusMessage: "Checking for destructive commands..."
- matcher: "Edit"
hooks:
- type: command
command: "bash ${CLAUDE_SKILL_DIR:-$HOME/.claude/skills/guard}/../freeze/bin/check-freeze.sh"
statusMessage: "Checking freeze boundary..."
- matcher: "Write"
hooks:
- type: command
command: "bash ${CLAUDE_SKILL_DIR:-$HOME/.claude/skills/guard}/../freeze/bin/check-freeze.sh"
statusMessage: "Checking freeze boundary..."
+ - matcher: "NotebookEdit"
+ hooks:
+ - type: command
+ command: "bash ${CLAUDE_SKILL_DIR:-$HOME/.claude/skills/guard}/../freeze/bin/check-freeze.sh"
+ statusMessage: "Checking freeze boundary..."
triggers:
- full safety mode
- guard against mistakes
- maximum safety
- guard mode
- lock it down
---
## When to invoke
Use when asked to "guard mode", "full safety", "lock it down", or "maximum safety".
# /guard — Full Safety Mode
Activates both destructive command warnings and directory-scoped edit restrictions.
This is `/careful` + `/freeze` in a single command.
**Dependency note:** This skill references hook scripts from the sibling `/careful` and `/freeze` skill directories. Both must be installed (they are installed together by the vibestack install script).
## Setup
Ask the user which directory to restrict edits to:
> "Guard mode: which directory should edits be restricted to? Destructive command warnings are always on. Files outside the chosen path will be blocked from editing."
- Once the user provides a path:
+ Once the user provides a path, set it with the shared state writer (see
+ `/freeze`):
```bash
- FREEZE_DIR=$(cd "<user-provided-path>" 2>/dev/null && pwd)
- FREEZE_DIR="${FREEZE_DIR%/}/"
- STATE_DIR="${VIBESTACK_HOME:-$HOME/.vibestack}"
- mkdir -p "$STATE_DIR"
- echo "$FREEZE_DIR" > "$STATE_DIR/freeze-dir.txt"
- echo "Freeze boundary set: $FREEZE_DIR"
+ bash "${CLAUDE_SKILL_DIR:-$HOME/.claude/skills/guard}/../freeze/bin/freeze-state.sh" set "<user-provided-path>"
```
+ Report guard mode active only if the command exits 0 and prints `FREEZE_DIR=`.
+ On `FREEZE_ERROR` (a mistyped or missing path, or `/`), tell the user no edit
+ boundary was set and ask for the path again. On `FREEZE_BUSY`, retry once the
+ other writer finishes; never write or delete the state file directly.
+
Tell the user:
- "**Guard mode active.** Two protections are now running:"
- "1. **Destructive command guard** — rm -rf, DROP TABLE, force-push, etc. warn before executing (you can override); catastrophic shapes (recursive delete of `/` or `~`, force-push to the default branch) are blocked outright"
- - "2. **Edit boundary** — file edits restricted to `<path>/`. Edits outside this directory are blocked."
+ - "2. **Edit boundary** — Edit, Write and NotebookEdit restricted to `<FREEZE_DIR>/`. Edits outside this directory are blocked."
- "To remove the edit boundary, run `/unfreeze`. To deactivate everything, end the session."
## What's protected
See `/careful` for the two decision tiers, the full pattern list, and the safe exceptions.
See `/freeze` for how edit boundary enforcement works.
Both hooks fail safe when they cannot read a tool payload — `/careful` asks,
- `/freeze` denies. Guard mode runs both, so an unreadable Edit or Write payload
- is blocked, not waved through.
+ `/freeze` denies. Guard mode runs both, so an unreadable Edit, Write or
+ NotebookEdit payload is blocked, not waved through.