guard

Warn on destructive commands and restrict file edits to a specified directory.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Full safety mode combining destructive-command warnings with directory-scoped edit restrictions to protect prod systems and debugging sessions.

Core Features & Use Cases

  • Destructive command warnings on risky operations (rm -rf, DROP TABLE, force-push, etc.) before execution.
  • Edit-boundary enforcement that blocks edits outside a user-specified path.
  • Guided setup and monitoring to ensure ongoing safety during maintenance and debugging.

Quick Start

Ask the user which directory to restrict edits to and set the freeze boundary accordingly.

Frequently Asked Questions about guard

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

FAQPage Schema
How do I prevent destructive commands from running in a production environment?

Preventing destructive commands in production requires pre-tool hooks that warn before executing risky operations like rm -rf, DROP TABLE, or force-push, stopping them before damage occurs.

What is the best way to restrict file edits to a specific directory during live debugging?

The best way to restrict file edits during live debugging is by setting a freeze boundary that blocks modifications outside a user-specified path, enforced via a state file.

Can I enforce edit boundaries for maintenance work without locking the entire system?

Yes, you can enforce edit boundaries for maintenance work without locking the entire system by specifying a freeze directory, which restricts modifications to that path alone.

What commands trigger destructive warnings during production safety mode?

Commands that trigger destructive warnings during production safety mode include rm -rf, DROP TABLE, and force-push, which are intercepted before execution to prevent accidental data loss.

How do I set up a freeze boundary to lock edits in a specific path?

To set up a freeze boundary and lock edits in a specific path, you specify the target directory during setup, which is stored in a state file to enforce the restriction.

Does production protection work alongside existing devops debugging workflows?

Yes, production protection works alongside devops debugging workflows by applying pre-tool hooks that warn on dangerous commands and restrict edits without disrupting ongoing maintenance tasks.