guard

Enforce safety checks on destructive commands and restrict edits to a directory.

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/antriksh-29/reddit-automation --skill guard-antriksh-29
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: guard
Source: https://github.com/antriksh-29/reddit-automation/tree/main/.claude/skills/gstack/guard
Command: npx skills add https://github.com/antriksh-29/reddit-automation --skill guard-antriksh-29

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually triggering safety controls for destructive commands and edits is error-prone; this skill provides a unified safety layer that warns before destructive actions and restricts edits to a specified directory.

Core Features & Use Cases

  • Destructive command warnings — rm -rf, DROP TABLE, force-push, and similar operations are warned before execution.
  • Directory edit boundary — edits are restricted to a user-selected directory, protecting resources outside of it.
  • Manual trigger flow — activate via /guard to enable safety mode during maintenance, debugging, or production touches.

Quick Start

Run /guard and specify the directory to protect from edits.

Frequently Asked Questions about guard

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I warn before destructive commands like rm -rf or DROP TABLE in live environments?

Warn before destructive commands by activating a safety layer that intercepts operations like rm -rf, DROP TABLE, and force-push, prompting confirmation before execution on live systems.

How do I restrict edits to a specific directory during production debugging?

Restrict edits to a specific directory during production debugging by configuring an edit boundary that protects resources outside the user-selected path from accidental modification.

Can I enforce safety checks for deployment maintenance without manual oversight?

Enforce safety checks for deployment maintenance automatically using PreToolUse hooks that validate safety boundaries via careful and freeze scripts, preventing accidental damage without manual oversight.

What is the best way to prevent accidental damage when running DevOps automation scripts?

Prevent accidental damage when running DevOps automation scripts by enabling a unified safety mode that applies guardrails, warning before destructive actions and bounding edits automatically.

Do I need to specify a directory to enable edit boundary protection?

You need to specify a directory to enable edit boundary protection, as the safety mechanism requires a user-selected path to enforce restrictions and protect external resources.