guard

Enforce directory-scoped edit protections and destructive-command warnings.

Updated Feb 5, 2026
One-click install
npx skills add https://github.com/CaltexBevo/ihe-pulse --skill guard-caltexbevo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: guard
Source: https://github.com/CaltexBevo/ihe-pulse/tree/main/.claude/skills/gstack.bak/guard
Command: npx skills add https://github.com/CaltexBevo/ihe-pulse --skill guard-caltexbevo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Full safety mode by combining destructive-command warnings with directory-scoped edit restrictions to prevent accidental production-impacting changes.

Core Features & Use Cases

  • Destructive-command warnings for dangerous operations (rm -rf, etc.)
  • Directory edit boundary enforcement to block edits outside a specified path
  • Integration with sibling /careful and /freeze skills to provide end-to-end safety guardrails

Quick Start

Tell me the directory to protect and enable guard mode; the system will activate destructive-command warnings and a file-edit boundary for that path.

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 commands like rm -rf from modifying production systems?

To prevent destructive commands from impacting production, you need safety guardrails that enforce warnings for dangerous operations like rm -rf. This system activates warnings and directory-scoped edit restrictions to block accidental production-impacting changes.

What are directory-scoped edit boundaries and how do they protect live environments?

Directory-scoped edit boundaries restrict file modifications to a specified folder path, blocking edits outside that boundary. This protects live environments by ensuring debugging or system modifications cannot accidentally alter files beyond the protected directory scope.

How do I set up edit boundaries and safety warnings for a specific folder during debugging?

To set up edit boundaries and safety warnings, provide the directory path you want to protect and enable guard mode. The system then coordinates with helper scripts and user prompts to activate destructive-command warnings and file-edit boundaries for that path.

Does this safety guardrail system work with other devops protection tools in the same workflow?

Yes, this system integrates with sibling /careful and /freeze skills to provide end-to-end safety guardrails. It coordinates with helper scripts and user prompts to deliver comprehensive destructive-command warnings and directory-scoped protections.

When should I use directory edit boundary enforcement for system protection?

Use directory edit boundary enforcement when modifying critical systems or debugging live environments. It provides tight control over a specified folder, preventing accidental production-impacting changes by combining destructive-command warnings with path-scoped edit restrictions.