guard

Combine destructive-command warnings with directory-bound edit restrictions.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/Ulanxx/mzstack --skill guard-ulanxx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: guard
Source: https://github.com/Ulanxx/mzstack/tree/main/guard
Command: npx skills add https://github.com/Ulanxx/mzstack --skill guard-ulanxx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Activates both destructive command warnings and directory-scoped edit restrictions by combining the capabilities of the /careful and /freeze skills, reducing risk during live-system work.

Core Features & Use Cases

  • Combined destructive command warnings and edit boundary enforcement for prod or debugging sessions.
  • Can be configured to restrict edits to a specified directory while still allowing necessary maintenance.
  • Works with the /careful and /freeze workflows to provide a unified safety layer.

Quick Start

Ask the user which directory should edits be restricted to, then enable guard mode to apply both protections.

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 like rm -rf during production debugging?

Preventing destructive commands like rm -rf requires combining destructive-command warnings with directory-bound edit restrictions. This safety layer activates during production maintenance to stop unsafe shell commands and out-of-scope file modifications.

What is the best way to lock edits to a specific directory during live-system maintenance?

Locking edits to a specific directory during live-system maintenance requires applying boundary-locked edit restrictions. This restricts file modifications to a designated folder while still allowing necessary production maintenance to proceed safely.

Do I need additional skills installed to enable directory-bound edit restrictions and destructive warnings?

Yes, enabling directory-bound edit restrictions and destructive warnings requires installing the sibling careful and freeze skills. You must also establish a target freeze directory to enforce the edit boundaries correctly.

Can I restrict file modifications to a specific folder while still allowing necessary production maintenance tasks?

Yes, you can restrict file modifications to a specific folder while allowing necessary production maintenance. Configuring boundary-locked edits prevents out-of-scope changes without blocking required debugging workflows within the designated directory.

When should I not use a combined safety layer for production security?

You should not use a combined safety layer for production security if you lack a defined target freeze directory or have not installed the required sibling skills. Without these prerequisites, the boundary-locked edit restrictions cannot be enforced.