guard

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

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/makyua-san/usecase-agent --skill guard-makyua-san
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: guard
Source: https://github.com/makyua-san/usecase-agent/tree/main/.claude/skills/guard
Command: npx skills add https://github.com/makyua-san/usecase-agent --skill guard-makyua-san

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides dual safety controls by warning on destructive commands and enforcing directory-bound edits to protect production and debugging environments.

Core Features & Use Cases

  • Destructive command warnings: prompts and blocks potentially dangerous commands unless overridden.
  • Directory edit boundary enforcement: restricts edits to a user-specified path to prevent accidental changes outside the safe zone.
  • Unified safety mode: combines careful and freeze into a single workflow for maximum protection in critical ops.

Quick Start

Provide the target directory to restrict edits to, and guard mode will activate both destructive-command warnings and the edit boundary.

Frequently Asked Questions about guard

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

FAQPage Schema
How do I prevent accidental destructive bash commands in production?▼

To prevent destructive bash commands in production, use a safety mode that warns and blocks potentially dangerous commands unless explicitly overridden. This ensures risky operations prompt confirmation before execution.

Can I restrict file edits to a specific directory during live system debugging?▼

Yes, you can restrict file edits to a specific directory during live system debugging by enforcing a directory-bound edit policy. This prevents accidental changes to files outside the designated safe zone.

What is the best way to combine command warnings and edit boundaries for prod maintenance?▼

The best way to combine command warnings and edit boundaries for prod maintenance is activating a unified safety mode. This merges destructive-command warnings with directory-bound edit policies to maximize protection.

How do I set up a safe zone for risky bash operations?▼

To set up a safe zone for risky bash operations, provide a target directory path to restrict edits to that location. The safety mode will then activate both destructive-command warnings and the edit boundary.

Do I need bash tools to enforce operational boundaries during debugging?▼

Yes, you need bash tools to enforce operational boundaries during debugging. The safety mode relies on bash tools to implement destructive-command warnings and directory-bound edit restrictions.