guard

Enforce safety boundaries for destructive commands and directory-scoped edits.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/2300031147/clawopencode --skill guard-2300031147
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: guard
Source: https://github.com/2300031147/clawopencode/tree/main/skills/guard
Command: npx skills add https://github.com/2300031147/clawopencode --skill guard-2300031147

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Combines destructive-command warnings with directory-scoped edit restrictions to prevent risky changes in production or during debugging, enabling safer operations and reduced blast radius.

Core Features & Use Cases

  • Destructive-command warnings for dangerous actions (rm -rf, DROP TABLE, force-push, etc.) and explicit prompts to confirm before execution.
  • Edit boundary enforcement that restricts edits to a user-specified directory, preventing accidental changes outside the scope.
  • PreToolUse hooks that invoke safety checks from sibling skills (/careful and /freeze) and surface clear status messages.

Quick Start

Provide the target directory path to activate guard mode and enforce 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 enforce edit boundaries and prevent changes outside a specific directory?

To enforce edit boundaries, you activate guard mode by providing a target directory path, which restricts file edits to that scope and prevents accidental modifications elsewhere in the file system.

How do I get warnings before executing destructive shell commands in production?

You get warnings for destructive shell commands through PreToolUse hooks that detect actions like rm -rf or DROP TABLE, surfacing clear status messages and requiring explicit confirmation before execution proceeds.

What is the best way to restrict file system edits during live production debugging?

The best way to restrict edits during live production debugging is to activate a full safety mode that combines destructive-command warnings with directory-scoped edit restrictions to reduce blast radius.

Can I integrate safety checks from other skills into my production protection workflow?

Yes, you can integrate safety checks from sibling skills like /careful and /freeze; the system invokes these checks via PreToolUse hooks to enforce safety boundaries across shell and live environments.

Do I need to specify a directory path to activate production protection for destructive commands?

Yes, you need to provide a target directory path to activate guard mode, which enforces the edit boundary and ensures destructive commands are intercepted before impacting areas outside that scope.