guard

Warn before destructive commands and restrict edits to a directory scope.

1|3|Updated Mar 19, 2026

Search Tags:#workflow #devops #safety #freeze #guard #destructive-warnings

Ready to run

npx skills add https://github.com/ekrishgupta/gemstack --skill guard-ekrishgupta

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: guard
Source: https://github.com/ekrishgupta/gemstack/tree/main/guard
Command: npx skills add https://github.com/ekrishgupta/gemstack --skill guard-ekrishgupta

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires careful, freeze.

What problem does it solve?

Destructive command warnings and directory-scoped edit restrictions are merged to prevent dangerous changes.

Core Features & Use Cases

Prevents destructive commands by warning users before execution
Enforces directory-bound edits to reduce accidental changes in sensitive areas
Works alongside related skills /careful and /freeze to provide end-to-end safety

Quick Start

Activate guard mode in a session and begin enforcing the safety boundaries immediately.

Frequently Asked Questions about guard

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

FAQPage Schema

What are destructive command warnings and how do they prevent data loss in production environments?▼

Directory-scoped edit restrictions enforce edit boundaries by confining modifications to approved paths. They reduce accidental changes in sensitive areas by blocking any write operations attempted outside the designated directory scope.

How do I enforce edit boundaries to prevent unauthorized changes in sensitive directories?▼

How do I set up guarded mode for maximum safety during live system debugging?▼

Guard works alongside the careful and freeze skills to provide end-to-end safety. Careful supplies pre-use check scripts to warn before destructive actions, while freeze enforces strict edit boundaries, together mitigating risky operations across development workflows.

Do I need the careful and freeze skills to use guard mode effectively?▼

When should I use directory-scoped edit restrictions in DevOps workflows?▼

Use directory-scoped edit restrictions when touching production environments or debugging live systems where preventing unauthorized edits is critical. They are essential for DevOps workflows that require strict boundaries to avoid accidental changes in sensitive areas.

What is the best way to prevent accidental destructive commands in development and production workflows?▼

The best way to prevent destructive commands is implementing a guarded mode that merges warnings with edit restrictions. Activating this mode enforces safety boundaries immediately, intercepting risky operations before they execute in critical environments.