guard

Files (3)

• SKILL.md
• SKILL.md.tmpl
• nexus.skill.yaml

SKILL.md (first lines)

<!-- AUTO-GENERATED from SKILL.md.tmpl — do not edit directly -->
<!-- Regenerate: bun run gen:skill-docs -->

# /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 Nexus setup script).

## 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:
```bash
FREEZE_DIR=$(cd "<user-provided-path>" 2>/dev/null && pwd)
echo "$FREEZE_DIR"
```

2. Ensure trailing slash and save to the freeze state file:
```bash
FREEZE_DIR="${FREEZE_DIR%/}/"
STATE_DIR="${CLAUDE_PLUGIN_DATA:-$HOME/.nexus}"
mkdir -p "$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.

## Output Contract

Report both protections and their current state:

- Destructive Bash command warnings are active through the `/careful` hook.
- Edit and Write operations are restricted to the absolute freeze boundary path.
- `/unfreeze` clears only the edit boundary; ending the session clears all hook state.

Do not claim guard mode is active unless the freeze boundary was written and the
destructive-command hook is part of this skill configuration.

## Verification Evidence

After setup, verify the boundary state file:

```bash
STATE_DIR="${CLAUDE_PLUGIN_DATA:-$HOME/.nexus}"
cat "$STATE_DIR/freeze-dir.txt"
```

The final response must include the saved absolute boundary path and confirm that
Bash commands will still be checked for destructive patterns.

From LaPaGaYo/nexus, MIT.

More from LaPaGaYo/nexus