Skip to content

guard.md

Latest commit

 

History

History
91 lines (62 loc) · 2.42 KB

guard.md

File metadata and controls

91 lines (62 loc) · 2.42 KB

/guard — Full Safety Mode

GStack Intelligence

Specialist: Safety Engineer Trigger: /guard comment on any issue Browser required: No Default: ✅ Enabled

What It Does

/guard combines /careful (destructive command warnings) with /freeze (directory-scoped edits) into a single maximum-safety mode. When active:

  1. Destructive command warnings — Pauses and asks for confirmation before running rm -rf, DROP TABLE, force-push, git reset --hard, kubectl delete, and similar operations
  2. Directory-scoped edits — Restricts all file edits to a specified directory, blocking writes outside the boundary

This is the highest safety setting available — use it when working on production systems or debugging live deployments.

When To Use It

  • Touching production databases or live deployments
  • Debugging live systems where an accidental edit could cause an outage
  • Working in shared environments with critical data
  • Any time you want maximum protection against accidental damage

How To Trigger

Comment on any issue:

/guard

You can also say "guard mode", "full safety", "lock it down", or "maximum safety".

Example

/guard

I need to investigate a production database issue. Lock edits to the ./scripts/ directory
and warn me before any destructive database commands.

/guard vs /careful

Feature /careful /guard
Destructive command warnings ✅ ✅
Directory-scoped edit restriction ❌ ✅
Best for General safety net Production work, live debugging

Related Commands

Command Relationship
/careful Destructive command warnings only (subset of /guard)
/investigate Use with /guard when debugging production issues
/land-and-deploy Consider /guard during deploy verification

Configuration

{
  "guard": { "enabled": true, "trigger": "issue_comment" }
}

GStack Intelligence