guard

Warn about destructive commands and restrict edits to a specified directory.

5|2|Updated Dec 27, 2025

Search Tags:#automation #devops #safety #risk-management #guard #destructive-warnings #edit-boundary

Ready to run

npx skills add https://github.com/agatx/serenada --skill guard-agatx

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: guard
Source: https://github.com/agatx/serenada/tree/main/.claude/skills/gstack/guard
Command: npx skills add https://github.com/agatx/serenada --skill guard-agatx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Full safety mode: destructive command warnings + directory-scoped edits. Combines /careful (warns before rm -rf, DROP TABLE, force-push, etc.) with /freeze (blocks edits outside a specified directory). Use for maximum safety when touching prod or debugging live systems. Use when asked to "guard mode", "full safety", "lock it down", or "maximum safety".

Core Features & Use Cases

Combines /careful with /freeze to warn before dangerous operations and enforce a user-defined edit boundary.
Works as a safety wrapper during critical maintenance, development, and risk-sensitive tasks.
Use case: enable guard mode to protect a production directory while you diagnose issues.

Quick Start

Choose the target directory for the edit boundary and enable destructive command warnings.

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 during server maintenance?▼

Preventing destructive commands during server maintenance requires enabling guard mode, which automatically warns before executing dangerous operations like rm -rf or DROP TABLE, ensuring you review risk-sensitive actions before they impact your environment.

How do I restrict file edits to a specific directory when debugging live systems?▼

To restrict file edits to a specific directory when debugging live systems, use guard mode to enforce an edit boundary. It blocks all modifications outside your user-defined target directory, protecting the rest of the file system from accidental changes.

Can I combine destructive command warnings with directory-scoped edit boundaries?▼

Yes, you can combine destructive command warnings with directory-scoped edit boundaries using guard mode. It integrates warning hooks for dangerous actions with edit boundary enforcement to provide maximum safety when touching production environments.

When should I enable full safety mode for DevOps and automation tasks?▼

You should enable full safety mode for DevOps and automation tasks when touching production directories, debugging live systems, or performing risk-sensitive maintenance. It provides maximum safety by locking down edits and warning before dangerous operations.

Does guard mode work for both local development and server environments?▼

Yes, guard mode works for both local development and server environments. It applies safety rails during maintenance, debugging, and risk-sensitive tasks wherever protection is critical, functioning as a safety wrapper across different environments.