gs-guard

name	gs:guard
version	0.1.0
description	Full safety mode: destructive command warnings + directory-scoped edits. Combines /gs:careful (warns before rm -rf, DROP TABLE, force-push, etc.) with /gs:freeze (blocks edits outside a specified directory). Use for maximum safety when touching prod or debugging live systems. Use when asked to "guard mode", "full safety", "lock it down", or "maximum safety". (gstack)
triggers	["full safety mode","guard against mistakes","maximum safety"]
allowed-tools	["Bash","Read","AskUserQuestion"]
hooks	{"PreToolUse":[{"matcher":"Bash","hooks":[{"type":"command","command":"bash ${CLAUDE_SKILL_DIR}/../careful/bin/check-careful.sh","statusMessage":"Checking for destructive commands..."}]},{"matcher":"Edit","hooks":[{"type":"command","command":"bash ${CLAUDE_SKILL_DIR}/../freeze/bin/check-freeze.sh","statusMessage":"Checking freeze boundary..."}]},{"matcher":"Write","hooks":[{"type":"command","command":"bash ${CLAUDE_SKILL_DIR}/../freeze/bin/check-freeze.sh","statusMessage":"Checking freeze boundary..."}]}]}
sensitive	true

Preamble (run first)

python "bin/gstack-boot.py" --skill guard | iex

Safety Advisory: This skill includes safety checks that check bash commands for destructive operations (rm -rf, DROP TABLE, force-push, git reset --hard, etc.) before execution, and verify file edits are within the allowed scope boundary before applying, and verify file writes are within the allowed scope boundary before applying. When using this skill, always pause and verify before executing potentially destructive operations. If uncertain about a command's safety, ask the user for confirmation before proceeding.

/gs:guard — Full Safety Mode

Activates both destructive command warnings and directory-scoped edit restrictions. This is the combination of /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 gstack setup script).

New-Item -ItemType Directory -Force ~/.gstack/analytics
echo '{"skill":"guard","ts":"'$(date -u +%Y-%m-%dT%H:%M:%SZ)'","repo":"'$(basename "$(git rev-parse --show-toplevel | Out-Null)" | Out-Null ; echo "unknown")'"}'  >> ~/.gstack/analytics/skill-usage.jsonl | Out-Null ; true

Setup

Ask the user which directory to restrict edits to. Use AskUserQuestion:

• Question: "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."
• Text input (not multiple choice) — the user types a path.

Once the user provides a directory path:

1. Resolve it to an absolute path:

FREEZE_DIR=$(cd "<user-provided-path>" | Out-Null ; pwd)
echo "$FREEZE_DIR"

2. Ensure trailing slash and save to the freeze state file:

FREEZE_DIR="${FREEZE_DIR%/}/"
STATE_DIR="${CLAUDE_PLUGIN_DATA:-$HOME/.gstack}"
New-Item -ItemType Directory -Force "$STATE_DIR"
echo "$FREEZE_DIR" > "$STATE_DIR/freeze-dir.txt"
echo "Freeze boundary set: $FREEZE_DIR"

Tell the user:

• "Guard mode active. Two protections are now running:"
• "1. Destructive command warnings — rm -rf, DROP TABLE, force-push, etc. will warn before executing (you can override)"
• "2. Edit boundary — file edits restricted to <path>/. 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 full list of destructive command patterns and safe exceptions. See /freeze for how edit boundary enforcement works.