guard

Warn before destructive commands and restrict file edits to approved directories.

Updated Feb 16, 2026
One-click install
npx skills add https://github.com/SeaLion-hub/DICEE --skill guard-sealion-hub
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: guard
Source: https://github.com/SeaLion-hub/DICEE/tree/main/.agents/skills/gstack/guard
Command: npx skills add https://github.com/SeaLion-hub/DICEE --skill guard-sealion-hub

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents risky edits and accidental data loss by warning on destructive commands and limiting edits to approved directories.

Core Features & Use Cases

  • Destructive command warnings warn before rm -rf, DROP TABLE, and similar actions when operating in sensitive environments.
  • Directory-bound edits restrict file modifications to a user-specified path, preventing changes outside trusted areas.
  • Synchronized safety with related skills coordinates with /careful and /freeze to provide layered protection during risky operations.

Quick Start

Activate guard mode by configuring the freeze boundary and running the guard command to enable safety protections.

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 in production environments?

You can prevent destructive commands by enforcing safety boundaries that warn before executing risky actions. This skill intercepts commands like rm -rf and DROP TABLE, issuing warnings and restricting file edits to approved directories to prevent accidental data loss.

How can I restrict file modifications to a specific directory boundary?

You can restrict file modifications by configuring a user-specified path boundary. The guard limits file edits to this approved directory, preventing any changes from occurring outside the trusted path in your development or production environment.

What are pre-execution hooks for command safety and how do they work?

Pre-execution hooks for command safety are mechanisms that intercept terminal commands before execution. They enforce boundary checks and trigger warnings for destructive actions, requiring integration with sibling safety scripts to coordinate layered protection during risky operations.

Can I use this command warning system alongside other safety scripts?

Yes, you can use this command warning system alongside other safety scripts. It synchronizes with related safety scripts to provide layered protection, requiring integration with sibling scripts via pre-execution hooks to coordinate warnings and boundary checks during risky operations.

How do I enable full safety mode to warn on destructive commands?

You can enable full safety mode to warn on destructive commands by configuring the freeze boundary and running the guard command. This activates the safety protections, applying directory-bound edits and pre-execution warnings across your environment.