guard

Monitor and restrict destructive commands and directory edits via hook scripts.

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/muhammadhamad1104/nuevo --skill guard-muhammadhamad1104
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: guard
Source: https://github.com/muhammadhamad1104/nuevo/tree/main/gstack/guard
Command: npx skills add https://github.com/muhammadhamad1104/nuevo --skill guard-muhammadhamad1104

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures that destructive commands are flagged and directory edits are restricted, reducing the risk of accidental data loss or system damage.

Core Features & Use Cases

  • Destructive Command Warnings: Alerts users before executing potentially harmful commands like 'rm -rf' or 'DROP TABLE'.
  • Directory-Scope Edits: Blocks file edits outside a specified directory, protecting critical system areas.
  • Use Case: When working in a production environment or during system debugging, use this Skill to prevent unintended actions that could lead to data loss or system instability.

Quick Start

To activate guard mode for a specific directory, run: guard /path/to/directory

Frequently Asked Questions about guard

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

FAQPage Schema
How do I prevent accidental data loss from destructive commands in a production environment?

To prevent accidental data loss from destructive commands, this Skill monitors execution and flags potentially harmful operations like 'rm -rf' or 'DROP TABLE' before they run. It acts as a safety mechanism to ensure system stability during critical debugging or production workflows.

Can I restrict file edits to a specific directory to protect system areas?

Yes, you can restrict file edits to a specific directory to protect critical system areas. The Skill enforces directory-scope limitations, blocking any file modifications attempted outside of your explicitly defined target path.

How do I activate directory protection for a specific path?

To activate directory protection for a specific path, run the command 'guard /path/to/directory'. This initializes the monitoring hooks that analyze command execution and restrict edits to the specified directory.

What mechanisms are used to monitor and control command execution?

The mechanism used to monitor and control command execution involves hook scripts. These scripts analyze commands as they are entered, intercepting and restricting destructive actions or out-of-scope directory edits to maintain system safety.

Does this command monitoring tool require any external dependencies?

No, this command monitoring tool does not require any external dependencies. It operates independently using internal hook scripts to analyze and control command execution without needing additional software packages.

When should I use a destructive command warning system?

You should use a destructive command warning system when working in environments where data integrity and system stability are paramount. It is specifically ideal for production environments or during sensitive system debugging to prevent unintended actions.